fix: organization dashboard issue

[pranalidhanavade]

What

• Resolved bug : Incorrect navigation from the “Dashboard” breadcrumb on the Organization Dashboard page.
• Removed 'dashboard' route from breadcrumb on organization dashboard.

Screen shots

1. Organization breadcrumb
   

2. Add passkey section
   

3. Delete icon changes for delete org page
   

---

Important

Fixes navigation issue in organization dashboard by removing 'dashboard' route and updates related components.

• Navigation Fix:
  • Removed 'dashboard' route from breadcrumb on organization dashboard.
  • Updated navigation paths in OrganizationCardList.tsx and OrganizationList.tsx to /organizations/${org.id}.
• Refactoring:
  • Replaced Trash2 with DeleteIcon in DeleteOrganizationCard.tsx.
  • Removed unused imports in user-auth-form.tsx and DeleteModal.tsx.
• Validation:
  • Added getDidValidationSchema in validationSchemas.ts for DID validation.
• UI Adjustments:
  • Adjusted button styles and loading states in AddPasskey.tsx and EditUserProfile.tsx.

^{This description was created by for 93c85a1. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 129c03b in 3 minutes and 48 seconds. Click for details.

• Reviewed 136 lines of code in 6 files
• Skipped 0 files when reviewing.
• Skipped posting 8 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. nextjs/src/features/dashboard/components/OrganizationCardList.tsx:149

• Draft comment:
  Navigation updated: using /organizations/${org.id} instead of /organizations/dashboard/${org.id}. Ensure consistency with all related links.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the author to ensure consistency with related links, which is a form of asking them to double-check something. This violates the rule against asking the author to ensure behavior is intended or to double-check things. Therefore, this comment should not be approved.

2. nextjs/src/features/organization/components/OrganizationList.tsx:114

• Draft comment:
  Corrected navigation: now using router.push(/organizations/${orgId}) to remove the '/dashboard' segment.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it simply states what was done without providing any actionable feedback or suggestions. It does not align with the rules for good comments.

3. nextjs/src/features/profile/components/EditUserProfile.tsx:223

• Draft comment:
  Input width changed from 'w-full' to a fixed 'w-3xl'. This might impact responsiveness; consider using responsive or fluid width classes.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% This is purely a UI styling change. The rules explicitly state not to comment on UI or styling changes, as we should assume the author made these changes intentionally. While the comment about responsiveness might be valid, it's not our place to question UI decisions. The comment does raise a valid technical concern about responsive design best practices. The change could potentially cause layout issues on different screen sizes. Despite the valid technical concern, the rules clearly state to NOT comment on pure frontend UI or styling changes. We must assume the author intentionally chose this styling approach. Delete this comment as it violates the rule about not commenting on UI and styling changes.

4. nextjs/src/features/verification/components/VerificationSchemasList.tsx:360

• Draft comment:
  RoleViewButton’s onClick now conditionally uses the updated route. For non-wallet states it navigates to /organizations/${organizationId}. Confirm this meets the desired navigation flow.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to confirm the navigation flow, which is against the rules. It does not provide a specific suggestion or point out a clear issue with the code. Therefore, it should be removed.

5. nextjs/src/features/wallet/WalletSpinupComponent.tsx:322

• Draft comment:
  Post spin-up redirection now uses router.push(/organizations/${orgId}) to reflect the updated URL structure.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining a change in the code without suggesting any action or asking for confirmation. It doesn't align with the rules for useful comments.

6. nextjs/src/features/wallet/WalletSpinupComponent.tsx:210

• Draft comment:
  Consider replacing window.location.href with router.push for redirection to preserve the SPA experience.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

7. nextjs/src/features/profile/components/EditUserProfile.tsx:226

• Draft comment:
  The class name "w-3xl" looks a bit unusual for a width utility. Please confirm that this is the intended Tailwind CSS class, and not a typographical error (for example, if "w-full" was intended).
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% The comment points out what appears to be a genuine error - 'w-3xl' is not a standard Tailwind width class. This could cause styling issues. The change from 'w-full' to 'w-3xl' appears to be a mistake. However, the comment is phrased as a request for confirmation rather than pointing out the actual issue. The project could have custom Tailwind extensions that define w-3xl. Also, the comment violates the rule about not asking for confirmations. While custom extensions are possible, this still warrants a comment - but it should be rephrased as a direct statement about the invalid class rather than asking for confirmation. The comment identifies a real issue but should be deleted because it's phrased as a request for confirmation. A new comment stating "w-3xl is not a valid Tailwind CSS width utility class" would be better.

8. nextjs/src/features/verification/components/VerificationSchemasList.tsx:358

• Draft comment:
  Typo: 'CRETAE_SCHEMA' appears to be a misspelling. Should it be 'CREATE_SCHEMA'?
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_PZ49HOrPqqgssgNt

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed f6d5f9e in 6 minutes and 54 seconds. Click for details.

• Reviewed 22 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. nextjs/src/features/wallet/DedicatedAgentLedgerConfig.tsx:437

• Draft comment:
  Changed the Indicio icon's src from SVG to PNG. Please verify that the PNG asset meets design and responsiveness requirements.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. nextjs/src/features/wallet/DedicatedAgentLedgerConfig.tsx:451

• Draft comment:
  The Polygon icon's alt text remains 'Indy Icon'. Consider updating it to 'Polygon Icon' for accuracy and accessibility.
• Reason this comment was not posted:
  Comment was on unchanged code.

Workflow ID: wflow_kaJD7vJy3iGxsncm

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 4125fc1 in 8 minutes and 43 seconds. Click for details.

• Reviewed 72 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. nextjs/src/features/wallet/DedicatedAgentLedgerConfig.tsx:60

• Draft comment:
  Remove the unused commented-out IValuesShared interface to clean up dead code.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. nextjs/src/features/wallet/DedicatedAgentLedgerConfig.tsx:93

• Draft comment:
  Renamed 'ledgerConfigData' to 'dedicatedLedgerConfigData' which improves clarity. Ensure that the renaming remains consistent throughout the file.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

3. nextjs/src/features/wallet/DedicatedAgentLedgerConfig.tsx:114

• Draft comment:
  Consistently using 'dedicatedLedgerConfigData' in the ledger sections (INDY, POLYGON, noLedger) is good. Verify that these changes align with usage elsewhere to prevent potential mismatches.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_huwrriVYaFRSLucG

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 24b3069 in 9 minutes and 7 seconds. Click for details.

• Reviewed 58 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. nextjs/src/features/wallet/DedicatedAgentLedgerConfig.tsx:148

• Draft comment:
  Good refactoring: the duplicate isSubmitDisabled function has been removed by moving it up. Consider using early returns for clarity.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. nextjs/src/features/wallet/DedicatedAgentLedgerConfig.tsx:298

• Draft comment:
  Removed duplicate definition of isSubmitDisabled. Verify that relocating this helper does not affect its usage context.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_YkvRONPThHvVmrwv

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed 16351db in 2 minutes and 6 seconds. Click for details.

• Reviewed 160 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 4 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. nextjs/src/features/organization/components/DeleteOrganizationCard.tsx:50

• Draft comment:
  Ensure the new DeleteIcon matches the previous Trash2 in size/styling for UI consistency.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. nextjs/src/features/wallet/DedicatedAgentLedgerConfig.tsx:188

• Draft comment:
  Confirm that getDidValidationSchema replicates all previous validation rules and error messages after the refactor.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to confirm that a function replicates previous behavior after a refactor. This falls under the rule of not asking the author to confirm their intention or to ensure behavior is intended. Therefore, this comment should be removed.

3. nextjs/src/features/wallet/LedgerConfig.tsx:154

• Draft comment:
  Verify that the includeLabel flag in getDidValidationSchema correctly applies the wallet label rules as before.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify the behavior of a flag, which is against the rules. It does not provide a specific suggestion or point out a specific issue.

4. nextjs/src/lib/validationSchemas.ts:24

• Draft comment:
  Typographical error: The validation message 'Method i' appears to be incomplete. Consider changing it to 'Method is required'.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_0MVxFOFGOsjs9WYZ

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Typo in error message: 'Method i' should likely be 'Method is required'.

Suggested change

	method: yup.string().required('Method i'),
	method: yup.string().required('Method is required'),

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed b8a4329 in 1 minute and 26 seconds. Click for details.

• Reviewed 197 lines of code in 5 files
• Skipped 0 files when reviewing.
• Skipped posting 7 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. nextjs/src/features/auth/components/user-auth-form.tsx:5

• Draft comment:
  Cleaned up lucide-react imports by consolidating into a single line. This improves code readability.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. nextjs/src/features/passkey/AddPasskey.tsx:45

• Draft comment:
  Initialized the loader state with false (instead of true) so that the UI doesn't show a loading state unnecessarily.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

3. nextjs/src/features/passkey/AddPasskey.tsx:242

• Draft comment:
  Both AlertComponent and a separate Alert with an AlertDescription are rendered with similar messages. Consider consolidating the alerts to avoid redundancy.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50% None

4. nextjs/src/features/passkey/AddPasskey.tsx:41

• Draft comment:
  Refactoring to pass 'email' as a prop and removing useSelector for userEmail improves component reusability and clarity.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

5. nextjs/src/features/passkey/DeleteModal.tsx:17

• Draft comment:
  Prop name 'onSucess' is misspelled. Consider renaming it to 'onSuccess' for clarity and consistency.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

6. nextjs/src/features/passkey/EditModal.tsx:87

• Draft comment:
  Replacing the inline SVG with the CheckCircle icon from lucide-react improves consistency and maintainability.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

7. nextjs/src/features/profile/components/UserProfile.tsx:95

• Draft comment:
  Passing the userEmail state to the AddPasskey component ensures proper context for passkey operations.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_1zXMRIBN8BVOhkcL

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.2% Duplication on New Code

See analysis details on SonarQube Cloud

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 93c85a1 in 41 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. nextjs/src/lib/validationSchemas.ts:24

• Draft comment:
  Fixed error message for 'method' field for clarity.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

Workflow ID: wflow_FbCyrgyO6hRDEL6l

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}