SN 261 #1460
SN 261 #1460
Conversation
📝 Walkthrough📝 WalkthroughWalkthroughThis pull request includes modifications to multiple SCSS files and JavaScript components, focusing on styling adjustments, new class additions, and component updates. Key changes involve setting background colors, adjusting paddings, and refining media queries in SCSS files. JavaScript files see updates in component imports, rendering logic, and validation handling. A new Changes
Possibly related PRs
Suggested reviewers
Poem
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 (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 10
🧹 Outside diff range comments (6)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js (1)
Line range hint
14-30: Remove commented out code.There are two sections of commented out code:
- The
transformURLfunction (lines 14-30)- A previous return statement (line 251)
Consider removing these commented out sections to improve code cleanliness and readability. If this code is needed for reference, consider moving it to documentation or version control comments.
Also applies to: 251-251
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/citizen/Home/UserProfile.js (5)
Line range hint
40-72: Consider optimizing state management.While the current state management is functional, consider the following optimizations:
- Use a single state object for user details instead of multiple state variables.
- Utilize the
useReducerhook for complex state management.- Memoize expensive computations or components using
useMemooruseCallback.These changes could improve performance and make the code more maintainable.
Line range hint
74-185: Refactor validation logic for better maintainability.The current validation logic is repeated across multiple functions. Consider creating a reusable validation utility:
- Create a separate validation utility file.
- Define validation rules for each field (name, email, password, etc.).
- Create a generic validation function that takes a field name and value as input.
This approach will centralize validation logic, making it easier to maintain and update.
Example:
// validation.js const validationRules = { userName: { pattern: /^[a-zA-Z ]+$/, maxLength: 50, errorMessage: "CORE_COMMON_PROFILE_NAME_INVALID" }, // ... other rules }; export const validateField = (fieldName, value) => { const rule = validationRules[fieldName]; if (!rule) return null; if (rule.pattern && !rule.pattern.test(value)) { return { type: "pattern", message: rule.errorMessage }; } // ... other validations return null; };Then use this in your component:
const setUserName = (value) => { setName(value); const error = validateField("userName", value); setErrors(prevErrors => ({ ...prevErrors, userName: error })); };This refactoring will significantly reduce code duplication and improve maintainability.
Line range hint
187-307: Refactor updateProfile function for better separation of concerns.The
updateProfilefunction is handling multiple responsibilities, making it complex and harder to maintain. Consider breaking it down into smaller, more focused functions:
- Create separate functions for validating profile data and password change.
- Extract the API call logic into a separate function.
- Use async/await consistently instead of mixing promises and async/await.
Example refactor:
const validateProfileData = () => { // Profile data validation logic }; const validatePasswordChange = () => { // Password change validation logic }; const updateUserProfile = async (userData) => { // API call to update user profile }; const changeUserPassword = async (passwordData) => { // API call to change password }; const updateProfile = async () => { setLoading(true); try { await validateProfileData(); if (changepassword) { await validatePasswordChange(); } const userData = { // ... user data }; await updateUserProfile(userData); if (changepassword) { const passwordData = { // ... password data }; await changeUserPassword(passwordData); } showToast("success", t("CORE_COMMON_PROFILE_UPDATE_SUCCESS"), 5000); } catch (error) { showToast("error", t(error.message), 5000); } finally { setLoading(false); } };This refactoring will improve readability, maintainability, and make the code easier to test.
Line range hint
309-929: Improve component structure and reusability.The current rendering logic is comprehensive but could be improved:
- Extract citizen and employee profile forms into separate components.
- Create a reusable FormField component to replace repetitive LabelFieldPair usage.
- Use a configuration object to define form fields, reducing repetitive code.
Example refactor:
const FormField = ({ label, children, error }) => ( <LabelFieldPair> <CardLabel>{label}</CardLabel> <div> {children} {error && <ErrorMessage message={error} />} </div> </LabelFieldPair> ); const fieldConfig = [ { name: 'name', label: 'CORE_COMMON_PROFILE_NAME', component: TextInput }, { name: 'gender', label: 'CORE_COMMON_PROFILE_GENDER', component: Dropdown }, // ... other fields ]; const ProfileForm = ({ userType, fields, values, errors, onChange }) => ( <> {fields.map(field => ( <FormField key={field.name} label={t(field.label)} error={errors[field.name]}> <field.component value={values[field.name]} onChange={(e) => onChange(field.name, e.target.value)} // ... other props /> </FormField> ))} </> ); // In the main component return ( <div className="user-profile"> {/* ... other JSX */} <ProfileForm userType={userType} fields={fieldConfig} values={{ name, gender, email, /* ... */ }} errors={errors} onChange={handleInputChange} /> {/* ... other JSX */} </div> );This refactoring will significantly reduce code duplication, improve readability, and make the component more maintainable.
Line range hint
1-929: Overall suggestions for component improvement
State Management: Consider using a custom hook or context for managing user profile state, separating concerns from the UI component.
Code Organization: Break down the large component into smaller, focused components (e.g., ProfilePicture, ProfileForm, PasswordChangeForm).
Styling: Move inline styles to a separate CSS file or use a CSS-in-JS solution for better maintainability and consistency.
Error Handling: Implement a more robust error handling mechanism, possibly using a custom hook or error boundary.
Accessibility: Ensure all interactive elements are keyboard accessible and have proper ARIA attributes.
Performance: Implement memoization for expensive computations or rerenders using React.memo, useMemo, or useCallback.
Testing: Add unit tests for the component and its logic to ensure reliability and ease of refactoring.
These improvements will enhance the overall quality, maintainability, and performance of the UserProfile component.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
⛔ Files ignored due to path filters (2)
micro-ui/web/micro-ui-internals/packages/css/package.jsonis excluded by!**/*.jsonmicro-ui/web/sandbox/package.jsonis excluded by!**/*.json
📒 Files selected for processing (7)
- micro-ui/web/micro-ui-internals/packages/css/src/components/table.scss (4 hunks)
- micro-ui/web/micro-ui-internals/packages/css/src/pages/employee/sandbox.scss (2 hunks)
- micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/citizen/FAQs/FaqComponent.js (2 hunks)
- micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/citizen/Home/UserProfile.js (2 hunks)
- micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js (3 hunks)
- micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js (1 hunks)
- micro-ui/web/public/index.html (1 hunks)
🧰 Additional context used
📓 Path-based instructions (4)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/citizen/FAQs/FaqComponent.js (1)
Pattern
**/*.js: checkmicro-ui/web/micro-ui-internals/packages/modules/core/src/pages/citizen/Home/UserProfile.js (1)
Pattern
**/*.js: checkmicro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js (1)
Pattern
**/*.js: checkmicro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js (1)
Pattern
**/*.js: check
🪛 Biome
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js
[error] 252-252: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.
Unsafe fix: Use a SelfClosingElement instead
(lint/style/useSelfClosingElements)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js
[error] 37-37: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 73-73: Missing key property for this element in iterable.
The order of the items may change, and having a key can help React identify which item was moved.
Check the React documentation.(lint/correctness/useJsxKeyInIterable)
🔇 Additional comments (11)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/citizen/FAQs/FaqComponent.js (2)
15-15:⚠️ Potential issueVerify intended behavior of ArrowForward component.
The conditional rendering of
ArrowForwardhas been removed, making it always visible regardless of theisOpenstate. While this simplifies the code, it might not be the intended behavior.Please confirm if this change is intentional. If not, consider reverting to the previous conditional rendering:
- <ArrowForward /> + {isOpen ? <ArrowForward /> : null}To verify the impact of this change, run the following script to check for similar patterns in other components:
#!/bin/bash # Description: Check for similar ArrowForward usage in other components # Test: Search for ArrowForward usage in other components. Expect: Various results to compare against. rg --type js -C 5 '<ArrowForward'
1-1: LGTM! Verify consistency of import change across the project.The import source for
ArrowForwardhas been updated to@egovernments/digit-ui-svg-components, which is likely part of a project-wide refactoring to separate SVG components. This change looks good, but it's important to ensure consistency across the entire project.To verify the consistency of this change across the project, run the following script:
✅ Verification successful
Import changes are consistent across the project.
All instances of
ArrowForwardhave been successfully updated to@egovernments/digit-ui-svg-components, and there are no remaining imports from the old package.🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for any remaining imports of ArrowForward from the old package # Test: Search for old imports of ArrowForward. Expect: No results. rg --type js 'import.*ArrowForward.*from.*@egovernments/digit-ui-components' # Test: Search for new imports of ArrowForward. Expect: Multiple results. rg --type js 'import.*ArrowForward.*from.*@egovernments/digit-ui-svg-components'Length of output: 14979
Script:
#!/bin/bash # Description: Check for any remaining imports of ArrowForward from the old package # Test: Search for old imports of ArrowForward. Expect: No results. rg --type js "import\s+{?\s*ArrowForward\s*}?\s+from\s+'@egovernments/digit-ui-components'" # Test: Search for new imports of ArrowForward. Expect: Multiple results. rg --type js "import\s+{?\s*ArrowForward\s*}?\s+from\s+'@egovernments/digit-ui-svg-components'"Length of output: 545
Script:
#!/bin/bash # Description: Verify import statements for ArrowForward # Test: Check for imports of ArrowForward from the old package. Expect: No results. ast-grep --lang javascript --pattern 'import { ArrowForward } from "@egovernments/digit-ui-components";' # Test: Check for imports of ArrowForward from the new package. Expect: At least one result. ast-grep --lang javascript --pattern 'import { ArrowForward } from "@egovernments/digit-ui-svg-components";'Length of output: 382
micro-ui/web/public/index.html (1)
10-10: 🧹 Nitpick (assertive)LGTM. Please verify visual changes and document update reason.
The update of @egovernments/digit-ui-css from 1.8.2-beta.34 to 1.8.2-beta.35 looks good. This minor version update likely includes bug fixes or small improvements.
Please verify that this update doesn't introduce any unexpected visual changes to the application. You can do this by comparing the appearance of key pages between the old and new versions.
Consider adding a brief comment in the PR description or commit message explaining the reason for this update and any notable changes it introduces. This will help with future maintenance and troubleshooting.
micro-ui/web/micro-ui-internals/packages/css/src/components/table.scss (1)
Line range hint
195-199: LGTM: Flexible width for the first column in reports tableThe change to set
min-width: unset;for the firstthelement in the.reports-tableclass is appropriate. This allows the first column to adjust its width based on content or layout requirements, providing more flexibility in the table design.micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js (3)
1-6: LGTM: Import statements are well-organized and necessary.The import statements are logically organized and include all necessary dependencies for the component's functionality.
91-91: LGTM: Default export is correct.The default export of the
QuickSetupcomponent is correct and follows common React practices.
1-91: Overall assessment: Well-structured component with minor improvement opportunities.The
QuickSetup.jsfile introduces a well-structured React component for displaying a sandbox guide. The implementation is solid and follows React best practices. The component is modular, using sub-components (CardCandFAQ) to render different sections based on the provided configuration.While the overall structure and functionality are sound, there are a few minor improvements that can be made:
- Externalizing the hardcoded FAQ data for better maintainability and internationalization.
- Adding key props to list items and fragments for optimized rendering.
- Using template literals instead of string concatenation for better readability.
Addressing these minor points will further enhance the quality and maintainability of the code.
🧰 Tools
🪛 Biome
[error] 37-37: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 73-73: Missing key property for this element in iterable.
The order of the items may change, and having a key can help React identify which item was moved.
Check the React documentation.(lint/correctness/useJsxKeyInIterable)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js (2)
57-75: LGTM: Well-structured configuration array.The
QuickSetupConfigarray is well-organized with clear sections for welcome messages and quick setup links. The use of translation keys supports internationalization, which is a good practice.
Line range hint
1-255: Summary of changes and overall assessment.This update introduces a new sandbox guide feature to the
QuickSetupConfigComponent. The main changes include:
- Introduction of a new
QuickSetupcomponent.- Creation of a detailed
cardConfigarray for the sandbox guide.- Updating the component's return statement to use the new
QuickSetupcomponent.The changes are well-structured and maintain good practices like internationalization support. The new
cardConfigprovides a comprehensive set of guides and FAQs, which should enhance the user experience.To further improve the code:
- Consider extracting the
cardConfigto a separate file.- Remove unused imports and commented-out code.
- Use a self-closing tag for the
QuickSetupcomponent.Overall, this appears to be a solid enhancement to the quick setup functionality.
🧰 Tools
🪛 Biome
[error] 252-252: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.
Unsafe fix: Use a SelfClosingElement instead
(lint/style/useSelfClosingElements)
micro-ui/web/micro-ui-internals/packages/css/src/pages/employee/sandbox.scss (1)
Line range hint
1-645: Summary of SCSS changesThe modifications to this SCSS file align well with the PR objectives, particularly in relation to the addition of new sidebar components and overall enhancements to the user interface. The changes primarily focus on style adjustments and additions, which should contribute to an improved user experience in the sandbox environment.
While no major issues were identified, there are opportunities for further refinement:
- Consider alternatives to
!importantdeclarations where possible to improve long-term maintainability.- Enhance cross-browser compatibility for custom scrollbar styles to ensure a consistent appearance across different browsers.
These changes appear to support the "addition of a new sidebar component" mentioned in the PR objectives and contribute to overall UI improvements.
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/citizen/Home/UserProfile.js (1)
Line range hint
1-39: LGTM: Imports and initial setup look good.The imports and initial setup of the component are well-organized. The component uses various UI components from the Digit UI library and React hooks for state management.
...-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js
Outdated
Show resolved
Hide resolved
...-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js
Outdated
Show resolved
Hide resolved
...-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js
Outdated
Show resolved
Hide resolved
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js
Show resolved
Hide resolved
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js
Outdated
Show resolved
Hide resolved
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js
Show resolved
Hide resolved
micro-ui/web/micro-ui-internals/packages/css/src/pages/employee/sandbox.scss
Show resolved
Hide resolved
micro-ui/web/micro-ui-internals/packages/css/src/pages/employee/sandbox.scss
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
📒 Files selected for processing (1)
- micro-ui/web/micro-ui-internals/packages/css/src/pages/employee/sandbox.scss (4 hunks)
🔇 Additional comments (1)
micro-ui/web/micro-ui-internals/packages/css/src/pages/employee/sandbox.scss (1)
628-645: Duplicate Comment: Cross-browser compatibility for custom scrollbar stylesA previous review comment addressed the need to ensure cross-browser compatibility for custom scrollbar styles. Please refer to the earlier suggestion to enhance consistency across different browsers.
micro-ui/web/micro-ui-internals/packages/css/src/pages/employee/sandbox.scss
Show resolved
Hide resolved
micro-ui/web/micro-ui-internals/packages/css/src/pages/employee/sandbox.scss
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Outside diff range comments (1)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js (1)
Line range hint
27-55: Remove unusedconfigEmployeeSideBarvariable.Since
configEmployeeSideBaris only referenced within the unusedQuickSetupConfig, you can remove theconfigEmployeeSideBarvariable and its related code to clean up the component.Apply this diff to remove the unused
configEmployeeSideBar:- const configEmployeeSideBar = data?.actions - .filter((e) => e.url === "card" && e.parentModule) - .reduce((acc, item) => { - const module = item.parentModule; - if (!acc[module]) { - acc[module] = { - module: module, - label: Digit.Utils.locale.getTransformedLocale(`${module}_CARD_HEADER`), - links: [], - }; - } - const linkUrl = Digit.Utils.transformURL(item.navigationURL, tenantId); - const queryParamIndex = linkUrl.indexOf("?"); - acc[module].links.push({ - link: queryParamIndex === -1 ? linkUrl : linkUrl.substring(0, queryParamIndex), - label: t(Digit.Utils.locale.getTransformedLocale(`${module}_LINK_${item.displayName}`)), - queryParams: queryParamIndex === -1 ? null : linkUrl.substring(queryParamIndex), - description: t(Digit.Utils.locale.getTransformedLocale(`${module}_LINK_${item.displayName}_DESCRIPTION`)), - }); - return acc; - }, {});Additionally, remove the conditional check dependent on
configEmployeeSideBar:- if (!configEmployeeSideBar) { - return ""; - }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
📒 Files selected for processing (2)
- micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js (3 hunks)
- micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js (1)
Pattern
**/*.js: checkmicro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js (1)
Pattern
**/*.js: check
🪛 Biome
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js
[error] 260-260: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.
Unsafe fix: Use a SelfClosingElement instead
(lint/style/useSelfClosingElements)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/QuickSetup.js
[error] 37-37: Template literals are preferred over string concatenation.
Unsafe fix: Use a template literal.
(lint/style/useTemplate)
[error] 73-73: Missing key property for this element in iterable.
The order of the items may change, and having a key can help React identify which item was moved.
Check the React documentation.(lint/correctness/useJsxKeyInIterable)
🔇 Additional comments (1)
micro-ui/web/micro-ui-internals/packages/modules/core/src/pages/employee/QuickStart/Config.js (1)
260-260: Apply previous suggestion to use a self-closing tag forQuickSetup.As previously mentioned, you can simplify the return statement by using a self-closing tag, since
QuickSetupdoes not have any children.Apply this diff:
- return <QuickSetup cardConfig={cardConfig}></QuickSetup>; + return <QuickSetup cardConfig={cardConfig} />;🧰 Tools
🪛 Biome
[error] 260-260: JSX elements without children should be marked as self-closing. In JSX, it is valid for any element to be self-closing.
Unsafe fix: Use a SelfClosingElement instead
(lint/style/useSelfClosingElements)
| ); | ||
| }; | ||
|
|
||
| const FAQ = ({ key, title, content, faqs }) => { |
There was a problem hiding this comment.
Remove key from props in FAQ component definition.
The key prop is a special attribute in React and is not accessible inside components via props.key. Including key in the component's props destructuring is unnecessary and may cause confusion. You can safely remove key from the props destructuring.
Apply this diff to fix the issue:
-const FAQ = ({ key, title, content, faqs }) => {
+const FAQ = ({ title, content, faqs }) => {📝 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.
| const FAQ = ({ key, title, content, faqs }) => { | |
| const FAQ = ({ title, content, faqs }) => { |
| sectionHeader: "WELCOME_TO_SANDBOX", | ||
| sections: [ | ||
| { | ||
| label: "SANDBOX_DESCRIPTION_1", | ||
| }, | ||
| { | ||
| label: "SANDBOX_DESCRIPTION_2", | ||
| }, | ||
| { | ||
| label: "SANDBOX_DESCRIPTION_3", | ||
| }, | ||
| ], | ||
| }, | ||
| { | ||
| sectionHeader:"QUICK_SETUP", | ||
| links:configEmployeeSideBar | ||
| } | ||
| ]; | ||
| return ( | ||
| <QuickSetupComponent config={QuickSetupConfig}></QuickSetupComponent> | ||
| ); | ||
| sectionHeader: "QUICK_SETUP", | ||
| links: configEmployeeSideBar, | ||
| }, | ||
| ]; |
There was a problem hiding this comment.
Remove unused QuickSetupConfig to improve code maintainability.
The QuickSetupConfig array defined in lines 58-75 is no longer used in the component, as the related return statement is commented out. Removing this unused code will enhance readability and maintainability.
Apply this diff to remove the unused QuickSetupConfig:
- const QuickSetupConfig = [
- {
- sectionHeader: "WELCOME_TO_SANDBOX",
- sections: [
- {
- label: "SANDBOX_DESCRIPTION_1",
- },
- {
- label: "SANDBOX_DESCRIPTION_2",
- },
- {
- label: "SANDBOX_DESCRIPTION_3",
- },
- ],
- },
- {
- sectionHeader: "QUICK_SETUP",
- links: configEmployeeSideBar,
- },
- ];📝 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.
| sectionHeader: "WELCOME_TO_SANDBOX", | |
| sections: [ | |
| { | |
| label: "SANDBOX_DESCRIPTION_1", | |
| }, | |
| { | |
| label: "SANDBOX_DESCRIPTION_2", | |
| }, | |
| { | |
| label: "SANDBOX_DESCRIPTION_3", | |
| }, | |
| ], | |
| }, | |
| { | |
| sectionHeader:"QUICK_SETUP", | |
| links:configEmployeeSideBar | |
| } | |
| ]; | |
| return ( | |
| <QuickSetupComponent config={QuickSetupConfig}></QuickSetupComponent> | |
| ); | |
| sectionHeader: "QUICK_SETUP", | |
| links: configEmployeeSideBar, | |
| }, | |
| ]; |
Summary by CodeRabbit
New Features
QuickSetupcomponent to display sandbox guides with FAQs.Improvements
Bug Fixes
Updates