chore: create/ update issue modal restructure.#5385
Conversation
WalkthroughThe recent changes enhance the modularity and user experience of issue management in the web application. New components for handling issue properties, an improved context provider for state management, and updates to modals and forms collectively streamline usability and maintainability. By leveraging React hooks and form management libraries, these updates ensure clarity and type safety, making the codebase more robust and easier to navigate. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Modal
participant Provider
participant Form
User->>Modal: Open Issue Modal
Modal->>Provider: Initialize context
Provider->>Form: Provide issue data and functions
Form->>User: Display issue fields
User->>Form: Fill in details
Form->>Provider: Update state
User->>Form: Submit issue
Form->>Provider: Validate and save data
Provider->>Modal: Update modal state
Modal->>User: Show confirmation
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 as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
Outside diff range, codebase verification and nitpick comments (6)
web/core/components/issues/issue-modal/components/description-editor.tsx (2)
3-24: Consider Import Optimization.The imports are well-organized by category, but consider using aliases for complex paths to improve readability.
44-59: Observer Usage May Be UnnecessaryThe
IssueDescriptionEditorcomponent imports theobserverHOC frommobx-react, but there is no evidence of MobX state (observable,action,computed) being used within the component. Consider removing theobserverwrapper if MobX state is not being utilized.
- File:
web/core/components/issues/issue-modal/components/description-editor.tsxAnalysis chain
Ensure Observer Usage is Necessary.
The
observerHOC is used, which implies this component might be observing MobX state changes. Verify that MobX state is indeed used within the component.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify MobX state usage within the IssueDescriptionEditor component. # Test: Search for observable state usage within the component. Expect: MobX state usage. rg --type tsx -A 5 'useObserver' web/core/components/issues/issue-modal/components/description-editor.tsxLength of output: 133
Script:
#!/bin/bash # Description: Verify MobX state usage within the IssueDescriptionEditor component. # Correct the file type to tsx and search for MobX-specific patterns. rg --type-add 'tsx:*.tsx' --type tsx 'observable|action|computed|mobx' web/core/components/issues/issue-modal/components/description-editor.tsxLength of output: 274
web/core/components/issues/issue-modal/components/default-properties.tsx (1)
3-30: Consider Import Optimization.The imports are well-organized by category, but consider using aliases for complex paths to improve readability.
web/core/components/issues/issue-modal/base.tsx (2)
10-20: Consider Import Optimization.The imports are well-organized by category, but consider using aliases for complex paths to improve readability.
Observer HOC Usage Might Be Unnecessary
The
CreateUpdateIssueModalBasecomponent imports theobserverHOC frommobx-react, but there is no evidence of MobX state usage within the component. Consider removing theobserverHOC if MobX state is not utilized.
- File:
web/core/components/issues/issue-modal/base.tsxAnalysis chain
Line range hint
24-54: Ensure Observer Usage is Necessary.The
observerHOC is used, which implies this component might be observing MobX state changes. Verify that MobX state is indeed used within the component.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify MobX state usage within the CreateUpdateIssueModalBase component. # Test: Search for observable state usage within the component. Expect: MobX state usage. rg --type tsx -A 5 'useObserver' web/core/components/issues/issue-modal/base.tsxLength of output: 108
Script:
#!/bin/bash # Description: Verify MobX state usage within the CreateUpdateIssueModalBase component. # Test: Search for MobX-related imports and usage patterns within the component. rg 'from .+mobx' -A 5 web/core/components/issues/issue-modal/base.tsxLength of output: 317
Script:
#!/bin/bash # Description: Further verify MobX state usage by searching for observable patterns and MobX state hooks. # Test: Search for observable patterns and MobX state hooks within the component. rg 'observable|computed|action|useLocalObservable|useAsObservableSource' web/core/components/issues/issue-modal/base.tsxLength of output: 251
web/core/components/issues/issue-modal/form.tsx (1)
3-30: Consider Import Optimization.The imports are well-organized by category, but consider using aliases for complex paths to improve readability.
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (31)
- web/ce/components/issues/issue-modal/additional-properties.tsx (1 hunks)
- web/ce/components/issues/issue-modal/index.ts (1 hunks)
- web/ce/components/issues/issue-modal/issue-type-select.tsx (1 hunks)
- web/ce/components/issues/issue-modal/provider.tsx (1 hunks)
- web/ce/types/index.ts (1 hunks)
- web/ce/types/issue-types/index.ts (1 hunks)
- web/ce/types/issue-types/issue-property-values.d.ts (1 hunks)
- web/core/components/issues/issue-layouts/properties/all-properties.tsx (1 hunks)
- web/core/components/issues/issue-modal/base.tsx (4 hunks)
- web/core/components/issues/issue-modal/components/default-properties.tsx (1 hunks)
- web/core/components/issues/issue-modal/components/description-editor.tsx (1 hunks)
- web/core/components/issues/issue-modal/components/index.ts (1 hunks)
- web/core/components/issues/issue-modal/components/parent-tag.tsx (1 hunks)
- web/core/components/issues/issue-modal/components/project-select.tsx (1 hunks)
- web/core/components/issues/issue-modal/components/title-input.tsx (1 hunks)
- web/core/components/issues/issue-modal/context/index.ts (1 hunks)
- web/core/components/issues/issue-modal/context/issue-modal.tsx (1 hunks)
- web/core/components/issues/issue-modal/draft-issue-layout.tsx (6 hunks)
- web/core/components/issues/issue-modal/form.tsx (1 hunks)
- web/core/components/issues/issue-modal/index.ts (1 hunks)
- web/core/components/issues/issue-modal/modal.tsx (1 hunks)
- web/core/constants/issue-modal.ts (1 hunks)
- web/core/hooks/context/use-issue-modal.tsx (1 hunks)
- web/ee/components/issues/issue-modal/additional-properties.tsx (1 hunks)
- web/ee/components/issues/issue-modal/index.ts (1 hunks)
- web/ee/components/issues/issue-modal/issue-type-select.tsx (1 hunks)
- web/ee/components/issues/issue-modal/provider.tsx (1 hunks)
- web/ee/types/index.ts (1 hunks)
- web/ee/types/issue-types/index.ts (1 hunks)
- web/ee/types/issue-types/issue-property-values.d.ts (1 hunks)
- web/helpers/issue-modal.helper.ts (1 hunks)
Files skipped from review due to trivial changes (12)
- web/ce/types/index.ts
- web/ce/types/issue-types/index.ts
- web/core/components/issues/issue-layouts/properties/all-properties.tsx
- web/core/components/issues/issue-modal/components/index.ts
- web/core/components/issues/issue-modal/context/index.ts
- web/core/constants/issue-modal.ts
- web/ee/components/issues/issue-modal/additional-properties.tsx
- web/ee/components/issues/issue-modal/issue-type-select.tsx
- web/ee/components/issues/issue-modal/provider.tsx
- web/ee/types/index.ts
- web/ee/types/issue-types/index.ts
- web/ee/types/issue-types/issue-property-values.d.ts
Additional context used
Biome
web/core/components/issues/issue-modal/components/project-select.tsx
[error] 35-35: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
web/core/components/issues/issue-modal/form.tsx
[error] 132-132: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 178-178: Do not access Object.prototype method 'hasOwnProperty' from target object.
It's recommended using Object.hasOwn() instead of using Object.hasOwnProperty().
See MDN web docs for more details.(lint/suspicious/noPrototypeBuiltins)
Additional comments not posted (31)
web/ce/components/issues/issue-modal/index.ts (1)
1-3: LGTM! Verify integration of new exports.The restructuring of exports enhances modularity. Ensure that the new modules (
provider,issue-type-select,additional-properties) are correctly implemented and integrated into the application.web/ee/components/issues/issue-modal/index.ts (1)
1-3: LGTM! Verify integration of new exports.The expanded exports enhance modularity and reusability. Ensure that the new modules (
provider,issue-type-select,additional-properties) are correctly integrated into the application.web/core/components/issues/issue-modal/index.ts (1)
1-5: LGTM! Verify integration of new exports.The expanded exports enhance the component's interface, promoting better integration and usability. Ensure that the new modules (
form,base,draft-issue-layout,context) are correctly integrated into the application.Verification successful
New exports are correctly integrated into the application. The specific exports from the new modules are actively used across various components, indicating successful integration.
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the integration of new exports in the codebase. # Test: Search for the usage of the new exports. Expect: Correct integration in relevant files. rg --type ts 'from "./form"|from "./base"|from "./draft-issue-layout"|from "./context"'Length of output: 2256
Script:
#!/bin/bash # Description: Check for the specific usage of exports from the new modules to ensure they are actively used. # Test: Search for specific exports usage from each module. rg --type ts 'IssueFormRoot|DraftIssueLayout|WebhookSecretKey|WebhookForm'Length of output: 3200
web/core/hooks/context/use-issue-modal.tsx (1)
5-9: LGTM!The
useIssueModalhook correctly handles the context and ensures it's used within the appropriate provider.web/core/components/issues/issue-modal/modal.tsx (1)
24-28: LGTM!The
CreateUpdateIssueModalcomponent is well-structured, using MobX and a provider for state management. The prop types are clearly defined.web/core/components/issues/issue-modal/context/issue-modal.tsx (1)
1-30: LGTM!The context and type definitions are well-structured and clear. This setup will facilitate state management for the issue modal effectively.
web/core/components/issues/issue-modal/components/title-input.tsx (1)
1-57: LGTM!The title input component is well-implemented with proper validation rules and error handling. The use of
react-hook-formis appropriate for managing form state.web/core/components/issues/issue-modal/components/parent-tag.tsx (1)
1-66: LGTM!The parent tag component effectively displays parent issue information and provides a mechanism to remove the parent. The use of
react-hook-formand MobX is well-integrated.web/core/components/issues/issue-modal/draft-issue-layout.tsx (1)
Line range hint
1-137: LGTM! VerifyonSubmitfunction usage.The changes enhance the draft issue management and state updates effectively. Ensure that all calls to
onSubmitin the codebase are updated to match the new signature withis_draft_issue.Verification successful
Verification Successful:
onSubmitFunction Signature UpdatedThe
onSubmitfunction indraft-issue-layout.tsxis correctly defined with the new signature, including theis_draft_issueparameter. Ensure that any other components interacting withDraftIssueLayoutare updated accordingly, although the current setup appears consistent.
- File:
web/core/components/issues/issue-modal/draft-issue-layout.tsx- Function Signature:
onSubmit: (formData: Partial<TIssue>, is_draft_issue?: boolean) => Promise<void>;Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify all calls to `onSubmit` match the new signature. # Test: Search for the function usage. Expect: Only occurrences with the updated signature. rg --type tsx -A 5 $'onSubmit'Length of output: 57
Script:
#!/bin/bash # Description: Verify all calls to `onSubmit` match the new signature. # Test: Search for the function usage. Expect: Only occurrences with the updated signature. rg 'onSubmit' -A 5Length of output: 125933
Script:
#!/bin/bash # Description: Verify the `onSubmit` function usage in `DraftIssueLayout` and related components to ensure it matches the new signature with `is_draft_issue`. # Search for the `DraftIssueLayout` component definition and its `onSubmit` usage. rg 'DraftIssueLayout' -A 20 # Search for `onSubmit` usage in the file containing `DraftIssueLayout`. fd 'draft-issue-layout.tsx' | xargs rg 'onSubmit'Length of output: 13045
web/core/components/issues/issue-modal/components/description-editor.tsx (6)
25-39: Review Type Definition for Completeness.The
TIssueDescriptionEditorPropstype definition is comprehensive, but ensure that all prop types are correctly defined and used throughout the component.
72-83: Ensure Proper Error Handling in handleKeyDown.The
handleKeyDownfunction checks if the editor is ready to discard changes. Ensure that this condition is always correctly evaluated and that the toast message provides adequate feedback.
94-131: Review AI Service Integration.The
handleAutoGenerateDescriptionfunction integrates with an AI service. Ensure that the service handles errors gracefully and that the user receives clear feedback in case of failures.
133-228: Review Conditional Rendering Logic.The conditional rendering of the loader and editor components is clear. Ensure that the conditions cover all possible states and that the user experience is seamless.
157-179: Ensure RichTextEditor Props are Correct.The
RichTextEditorcomponent receives several props. Verify that all props are correctly passed and that the component behaves as expected.
180-223: Review Button and Popover Accessibility.Ensure that the buttons and popovers are accessible, with appropriate aria attributes and keyboard navigation support.
web/core/components/issues/issue-modal/components/default-properties.tsx (4)
31-44: Review Type Definition for Completeness.The
TIssueDefaultPropertiesPropstype definition is comprehensive, but ensure that all prop types are correctly defined and used throughout the component.
62-74: Review Derived Values Logic.The calculation of
minDateandmaxDateis straightforward. Ensure that these values are used correctly in theDateDropdowncomponents.
75-323: Review Dropdown Components and Modal Logic.Ensure that all dropdown components and the
ParentIssuesListModalare correctly configured and handle state changes appropriately.
46-60: Ensure Observer Usage is Necessary.The
observerHOC is used, which implies this component might be observing MobX state changes. Verify that MobX state is indeed used within the component.web/core/components/issues/issue-modal/base.tsx (3)
Line range hint
54-244: Review New Hook Integration.The
useIssueModalhook is integrated into the component. Ensure that it enhances functionality as expected and that all new logic is correctly implemented.
185-192: Review Property Values Handling Logic.The
handleCreateUpdatePropertyValuesfunction is called after issue creation. Ensure that it correctly handles property values and integrates seamlessly with the rest of the logic.
238-243: Review Property Values Handling Logic.The
handleCreateUpdatePropertyValuesfunction is called after issue updates. Ensure that it correctly handles property values and integrates seamlessly with the rest of the logic.web/core/components/issues/issue-modal/form.tsx (9)
32-47: Review Default Values for Completeness.The
defaultValuesobject is comprehensive, but ensure that all default values are correctly set and used throughout the form.
49-59: Review Prop Types for Completeness.The
IssueFormPropsinterface is comprehensive, but ensure that all prop types are correctly defined and used throughout the component.
106-125: Review Project ID Change Logic.The logic for resetting fields on project ID change is clear. Ensure that all necessary fields are reset and that the user experience is seamless.
127-145: Review Issue Type ID Update Logic.The logic for updating the issue type ID on project ID change is clear. Ensure that the correct issue type ID is set and validated.
Tools
Biome
[error] 132-132: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
147-192: Review Form Submission Logic.The
handleFormSubmitfunction includes several checks and validations. Ensure that all conditions are correctly evaluated and that the form submission is robust.Tools
Biome
[error] 178-178: Do not access Object.prototype method 'hasOwnProperty' from target object.
It's recommended using Object.hasOwn() instead of using Object.hasOwnProperty().
See MDN web docs for more details.(lint/suspicious/noPrototypeBuiltins)
204-224: Review Parent Issue Logic.The logic for handling parent issues is clear. Ensure that the selected parent issue is correctly set and that all dependencies are resolved.
226-233: Review Dirty State Logic.The logic for handling the dirty state is straightforward. Ensure that all changes are correctly tracked and that the form state is accurately represented.
235-404: Review Form Layout and Components.Ensure that all form components are correctly configured and handle state changes appropriately. Verify that the layout is responsive and accessible.
61-72: Ensure Observer Usage is Necessary.The
observerHOC is used, which implies this component might be observing MobX state changes. Verify that MobX state is indeed used within the component.
| export type TIssuePropertyValues = object; | ||
| export type TIssuePropertyValueErrors = object; |
There was a problem hiding this comment.
Consider using more specific type definitions.
Defining TIssuePropertyValues and TIssuePropertyValueErrors as object does not provide type safety or clarity. Consider defining these types with specific properties to enhance maintainability and readability.
| import { ISSUE_FORM_TAB_INDICES } from "@/constants/issue-modal"; | ||
|
|
||
| export const getTabIndex = (key: string) => ISSUE_FORM_TAB_INDICES.findIndex((tabIndex) => tabIndex === key) + 1; |
There was a problem hiding this comment.
Add error handling for getTabIndex.
The function assumes the key exists in ISSUE_FORM_TAB_INDICES. Consider adding error handling for cases where the key is not found to prevent unexpected behavior.
export const getTabIndex = (key: string) => {
const index = ISSUE_FORM_TAB_INDICES.findIndex((tabIndex) => tabIndex === key);
return index !== -1 ? index + 1 : -1; // Return -1 or handle the error appropriately
};Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| import { ISSUE_FORM_TAB_INDICES } from "@/constants/issue-modal"; | |
| export const getTabIndex = (key: string) => ISSUE_FORM_TAB_INDICES.findIndex((tabIndex) => tabIndex === key) + 1; | |
| import { ISSUE_FORM_TAB_INDICES } from "@/constants/issue-modal"; | |
| export const getTabIndex = (key: string) => { | |
| const index = ISSUE_FORM_TAB_INDICES.findIndex((tabIndex) => tabIndex === key); | |
| return index !== -1 ? index + 1 : -1; // Return -1 or handle the error appropriately | |
| }; |
| workspaceSlug: string; | ||
| }; | ||
|
|
||
| export const IssueAdditionalProperties: React.FC<TIssueAdditionalPropertiesProps> = () => <></>; |
There was a problem hiding this comment.
Implement the component logic.
The IssueAdditionalProperties component is currently a placeholder. Consider implementing the component logic to utilize the defined props.
| handleFormChange: () => void; | ||
| }; | ||
|
|
||
| export const IssueTypeSelect: React.FC<TIssueTypeSelectProps> = () => <></>; |
There was a problem hiding this comment.
Implement the component logic.
The IssueTypeSelect component is currently a placeholder. Consider implementing the component logic to utilize the defined props.
| value={{ | ||
| issuePropertyValues: {}, | ||
| setIssuePropertyValues: () => {}, | ||
| issuePropertyValueErrors: {}, | ||
| setIssuePropertyValueErrors: () => {}, | ||
| getIssueTypeIdOnProjectChange: () => null, | ||
| handlePropertyValuesValidation: () => true, | ||
| handleCreateUpdatePropertyValues: () => Promise.resolve(), | ||
| }} |
There was a problem hiding this comment.
Consider implementing default functions.
The default functions provided in the context are currently no-ops. Consider implementing these functions to provide meaningful default behavior.
| required: true, | ||
| }} | ||
| render={({ field: { value, onChange } }) => | ||
| projectsWithCreatePermissions && projectsWithCreatePermissions[value!] ? ( |
There was a problem hiding this comment.
Use optional chaining for safety.
Consider using optional chaining to safely access projectsWithCreatePermissions[value!] to prevent potential runtime errors if projectsWithCreatePermissions is undefined.
- projectsWithCreatePermissions && projectsWithCreatePermissions[value!]
+ projectsWithCreatePermissions?.[value!]Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| projectsWithCreatePermissions && projectsWithCreatePermissions[value!] ? ( | |
| projectsWithCreatePermissions?.[value!] ? ( |
Tools
Biome
[error] 35-35: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
There was a problem hiding this comment.
Actionable comments posted: 2
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (4)
- web/ce/components/issues/issue-modal/provider.tsx (1 hunks)
- web/core/components/issues/issue-modal/components/description-editor.tsx (1 hunks)
- web/core/components/issues/issue-modal/context/issue-modal.tsx (1 hunks)
- web/core/components/issues/issue-modal/form.tsx (1 hunks)
Files skipped from review due to trivial changes (1)
- web/ce/components/issues/issue-modal/provider.tsx
Files skipped from review as they are similar to previous changes (2)
- web/core/components/issues/issue-modal/components/description-editor.tsx
- web/core/components/issues/issue-modal/context/issue-modal.tsx
Additional context used
Biome
web/core/components/issues/issue-modal/form.tsx
[error] 139-139: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
[error] 185-185: Do not access Object.prototype method 'hasOwnProperty' from target object.
It's recommended using Object.hasOwn() instead of using Object.hasOwnProperty().
See MDN web docs for more details.(lint/suspicious/noPrototypeBuiltins)
Additional comments not posted (4)
web/core/components/issues/issue-modal/form.tsx (4)
1-48: Imports and Default Values Look Good.The imports are well-organized by category, and the default values for the form are appropriately defined.
50-60: Props Interface is Well-Defined.The
IssueFormPropsinterface clearly defines the necessary props for the component.
62-132: Component Definition and Hooks Look Good.The
IssueFormRootcomponent effectively uses React hooks for managing state, refs, and side effects. Dependency arrays are appropriately considered.
242-427: Rendering Logic is Well-Structured.The rendering logic effectively uses conditional rendering and component composition.
| }; | ||
|
|
||
| // this condition helps to move the issues from draft to project issues | ||
| if (formData.hasOwnProperty("is_draft")) submitData.is_draft = formData.is_draft; |
There was a problem hiding this comment.
Use Object.hasOwn() for Prototype Safety.
Replace hasOwnProperty with Object.hasOwn() for safer prototype access.
- if (formData.hasOwnProperty("is_draft")) submitData.is_draft = formData.is_draft;
+ if (Object.hasOwn(formData, "is_draft")) submitData.is_draft = formData.is_draft;Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| if (formData.hasOwnProperty("is_draft")) submitData.is_draft = formData.is_draft; | |
| if (Object.hasOwn(formData, "is_draft")) submitData.is_draft = formData.is_draft; |
Tools
Biome
[error] 185-185: Do not access Object.prototype method 'hasOwnProperty' from target object.
It's recommended using Object.hasOwn() instead of using Object.hasOwnProperty().
See MDN web docs for more details.(lint/suspicious/noPrototypeBuiltins)
| useEffect(() => { | ||
| const issueTypeId = watch("type_id"); | ||
|
|
||
| // if data is present, set active type id to the type id of the issue | ||
| if (data && data.type_id) { |
There was a problem hiding this comment.
Use Optional Chaining for Safety.
Consider using optional chaining to safely access data.type_id.
- if (data && data.type_id) {
+ if (data?.type_id) {Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| useEffect(() => { | |
| const issueTypeId = watch("type_id"); | |
| // if data is present, set active type id to the type id of the issue | |
| if (data && data.type_id) { | |
| useEffect(() => { | |
| const issueTypeId = watch("type_id"); | |
| // if data is present, set active type id to the type id of the issue | |
| if (data?.type_id) { |
Tools
Biome
[error] 139-139: Change to an optional chain.
Unsafe fix: Change to an optional chain.
(lint/complexity/useOptionalChain)
2 participants
Summary by CodeRabbit
New Features
IssueDescriptionEditor,IssueTypeSelect,IssueModalProvider, andIssueFormRoot.Bug Fixes
Documentation
Chores