-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert EditFieldModal.jsx to tsx #3865
Conversation
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller
Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
WalkthroughThe pull request modifies the Possibly related PRs
Suggested labels
Suggested reviewers
Warning There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure. 🔧 eslint
packages/desktop-client/src/components/modals/EditFieldModal.tsxOops! Something went wrong! :( ESLint: 8.57.1 ESLint couldn't find the plugin "eslint-plugin-eslint-plugin". (The package "eslint-plugin-eslint-plugin" was not found when loaded as a Node module from the directory "/packages/eslint-plugin-actual".) It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
The plugin "eslint-plugin-eslint-plugin" was referenced from the config file in "packages/eslint-plugin-actual/.eslintrc.js". If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (2)
packages/desktop-client/src/components/modals/EditFieldModal.tsx (2)
1-1
: Optimize React importsConsider using named imports directly instead of the default React import to align with modern React practices.
-import React, { type CSSProperties, useRef, useState } from 'react'; +import { type CSSProperties, useRef, useState } from 'react';🧰 Tools
🪛 GitHub Check: lint
[warning] 1-1:
Imports "React" are only used as type
42-42
: Consider using a more specific type for the input refWhile
HTMLInputElement
is correct, consider creating a type that includes only the methods and properties you actually use (focus) for better type safety.-const noteInputRef = useRef<HTMLInputElement | null>(null); +type InputRefType = { + focus: () => void; +}; +const noteInputRef = useRef<InputRefType | null>(null);
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (1)
upcoming-release-notes/3865.md
is excluded by!**/*.md
📒 Files selected for processing (1)
packages/desktop-client/src/components/modals/EditFieldModal.tsx
(6 hunks)
🧰 Additional context used
🪛 GitHub Check: lint
packages/desktop-client/src/components/modals/EditFieldModal.tsx
[warning] 1-1:
Imports "React" are only used as type
[warning] 66-66:
Using default React import is discouraged, please use named exports directly instead
🔇 Additional comments (3)
packages/desktop-client/src/components/modals/EditFieldModal.tsx (3)
26-34
: LGTM! Well-structured type definition
The EditFieldModalProps
type is well-defined with clear type annotations for all props, including the union type for the mode
parameter.
207-213
: LGTM! Proper ref and event handling
The Input component implementation with ref forwarding and event handling is well done.
Line range hint 1-275
: Overall excellent TypeScript conversion
The conversion to TypeScript has been done thoroughly with proper type annotations, maintaining the original functionality while adding type safety. The component structure, prop types, and event handlers are well-typed and follow TypeScript best practices.
🧰 Tools
🪛 GitHub Check: lint
[warning] 66-66:
Using default React import is discouraged, please use named exports directly instead
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
packages/desktop-client/src/components/modals/EditFieldModal.tsx (2)
1-1
: Use named imports from ReactConsider using named imports directly from React instead of the default import.
-import React, { type CSSProperties, useRef, useState } from 'react'; +import { type CSSProperties, useRef, useState, type ReactNode } from 'react';🧰 Tools
🪛 GitHub Check: lint
[warning] 1-1:
Imports "React" are only used as type
140-140
: Consider extracting duplicated button stylesThe button styles and focus logic are duplicated across three buttons. Consider extracting this into a reusable component or shared styles.
// Example shared component: type NoteButtonProps = { mode: NoteAmendMode; currentMode: NoteAmendMode; label: string; onPress: () => void; }; const NoteButton: React.FC<NoteButtonProps> = ({ mode, currentMode, label, onPress }) => ( <Button style={{ padding: '5px 10px', width: '33.33%', backgroundColor: theme.menuBackground, marginRight: 5, fontSize: 'inherit', ...(currentMode === mode ? { backgroundColor: theme.buttonPrimaryBackground, color: theme.buttonPrimaryText, ':hover': { backgroundColor: theme.buttonPrimaryBackgroundHover, color: theme.buttonPrimaryTextHover, }, } : { backgroundColor: theme.buttonNormalBackground, color: theme.buttonNormalText, ':hover': { backgroundColor: theme.buttonNormalBackgroundHover, color: theme.buttonNormalTextHover, }, }), }} onPress={onPress} > {label} </Button> );Also applies to: 171-171, 202-202
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
packages/desktop-client/src/components/modals/EditFieldModal.tsx
(6 hunks)
🧰 Additional context used
🪛 GitHub Check: lint
packages/desktop-client/src/components/modals/EditFieldModal.tsx
[warning] 1-1:
Imports "React" are only used as type
[warning] 46-46:
Replace ⏎····value:·string,⏎····mode?:·NoteAmendMode,⏎··
with value:·string,·mode?:·NoteAmendMode
[warning] 68-68:
Using default React import is discouraged, please use named exports directly instead
[warning] 75-75:
Replace ⏎····'replace',⏎··
with 'replace'
🔇 Additional comments (4)
packages/desktop-client/src/components/modals/EditFieldModal.tsx (4)
26-36
: LGTM! Well-structured type definitions
The type definitions for NoteAmendMode
and EditFieldModalProps
are well-structured and provide good type safety.
38-44
: LGTM! Clean TypeScript implementation
The component props destructuring and hook initialization are well-typed and properly implemented.
46-64
: LGTM! Type-safe event handlers
The event handlers are well-typed and properly handle different input types.
🧰 Tools
🪛 GitHub Check: lint
[warning] 46-46:
Replace ⏎····value:·string,⏎····mode?:·NoteAmendMode,⏎··
with value:·string,·mode?:·NoteAmendMode
Line range hint 67-277
: LGTM! Well-structured modal implementation
The modal implementation is well-organized with proper TypeScript types and responsive handling.
No description provided.