Cleanup refactor

[Kodylow]

Groups components, no changes besides imports

Summary by CodeRabbit

• Refactor
  • Reorganized import paths for various components to reflect new directory structure.
  • Enhanced code readability and project maintainability by grouping components into more specific directories under components/dashboard.

These changes do not affect functionality but improve the organization of the codebase, making it easier for future development and maintenance.

[coderabbitai]

Warning

Review failed

The pull request is closed.

Walkthrough

Walkthrough

The changes primarily involve reorganizing import paths to reflect a new directory structure in the codebase. Components are now imported from more specific directories under components/dashboard instead of generic paths. Additionally, this restructuring affects various hooks, utility functions, and type definitions to ensure they are correctly referenced from their new locations.

Changes

Files (Path shortened with ... if needed)	Change Summary
.../FederationAdmin.tsx	Reorganized import statements to reflect new component locations under components/dashboard.
.../BalanceCard.tsx, .../FederationInfoCard.tsx	Updated import path for useAdminContext from ../hooks to ../../../hooks.
.../DownloadBackup.tsx	Updated import paths for useAdminContext and hexToBlob.
.../GatewaysCard.tsx, .../MetaManager.tsx, .../ProposedMetas.tsx, .../ViewConsensusMeta.tsx	Updated import paths for ModuleRpc and useAdminContext to reflect new locations.
.../BalanceTable.tsx	Added BalanceTable component and introduced corresponding types.
.../ConnectGuardians.tsx, .../RoleSelector.tsx, .../RunDKG.tsx	Adjusted import paths for hooks, types, and utility functions for correct module resolution.
.../SetConfiguration.tsx	Updated import paths for hooks, types, utility functions, and components to reflect the new file structure.
.../SetupComplete.tsx, .../SetupProgress.tsx, .../VerifyGuardians.tsx	Changed import paths for hooks, types, and utility functions to point to new locations.
.../FederationSetup.tsx	Updated import paths for various setup components to reflect the new structure under components/setup.

Sequence Diagram(s)

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (3)

apps/guardian-ui/src/components/setup/VerifyGuardians.tsx (1)

Line range hint 236-347: This else clause can be omitted because previous branches break early.

-  } else {
+  {

apps/guardian-ui/src/components/dashboard/tabs/meta/ProposedMetas.tsx (1)

Line range hint 181-187: This else clause can be omitted because previous branches break early.

-  } else {
+  {

apps/guardian-ui/src/components/setup/SetConfiguration.tsx (1)

Line range hint 216-216: Avoid the use of spread (...) syntax on accumulators as it causes a time complexity of O(n^2). Consider methods such as .splice or .push instead.

-            meta: metaFields.reduce((acc, [key, val]) => ({ ...acc, [key]: val }), {}),
+            meta: metaFields.reduce((acc, [key, val]) => { acc[key] = val; return acc; }, {}),

[tvolk131]

This doesn't appear to be used anywhere yet and isn't related to the rest of the changes. Should this be moved to a separate PR?