Skip to content

Claudio/fix hydration#265

Merged
claudfuen merged 7 commits into
mainfrom
claudio/fix-hydration
Apr 3, 2025
Merged

Claudio/fix hydration#265
claudfuen merged 7 commits into
mainfrom
claudio/fix-hydration

Conversation

@claudfuen

@claudfuen claudfuen commented Apr 3, 2025

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • New Features
    • Artifacts now display detailed, dynamic information with context-specific navigation paths.
    • Requirements and controls tables have been updated to show framework details with enhanced sorting and search capabilities.
    • The evidence review section now dynamically reflects the current evidence’s title and description.
    • UI messaging has been refreshed by replacing previous terms with “Linked Artifacts” and “Linked Requirements.”

…ls view

- Renamed "Mapped Requirements" to "Linked Requirements" in controls table and related components.
- Updated error logging message for fetching artifacts to reflect new terminology.
- Adjusted localization strings to replace "related artifacts" with "Linked Artifacts".
…ation

- Updated RequirementsTable to include framework instance details in the requirements mapping.
- Modified SingleControl component to reflect changes in requirementsMapped structure.
- Adjusted getControl function to include framework instance in the requirements mapping.
- Updated localization strings to include new framework and requirement identifiers.
…ting

- Refactored RequirementsTable to replace requirementId with id for improved clarity.
- Enhanced cell rendering to display both framework and requirement names.
- Removed unnecessary sorting logic for framework and requirementId columns.
- Updated initial sorting state to reflect new id accessor.
…rtifact handling

- Refactored ArtifactsTable to utilize a new structure for artifacts, integrating evidence and policy details.
- Updated SingleControl component to reflect changes in relatedArtifacts structure.
- Simplified getRelatedArtifacts function to return artifacts directly without transformation.
- Enhanced sorting and filtering logic in ArtifactsTable for better user experience.
…mproved clarity

- Removed Alert component from EvidenceDetails to streamline the display of evidence information.
- Updated ReviewSection to show evidence name in the header and description in the subtitle for better context.
… data display

- Added RequirementsTable component to SingleControl for displaying control requirements.
- Removed commented-out code for RequirementsTable to clean up the component structure.
@vercel

vercel Bot commented Apr 3, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
app 🔄 Building (Inspect) Visit Preview 💬 Add feedback Apr 3, 2025 9:58pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
comp-portal ⬜️ Skipped (Inspect) Apr 3, 2025 9:58pm

@CLAassistant

CLAassistant commented Apr 3, 2025

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@claudfuen claudfuen merged commit 6aa663a into main Apr 3, 2025
@coderabbitai

coderabbitai Bot commented Apr 3, 2025

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates several control components by refining and standardizing their data types and logic. Artifact and requirement structures now include additional properties (such as evidence, policy, and frameworkInstance) and use updated sorting, filtering, and routing functions. Adjustments include renaming terminology from “Mapped/Related” to “Linked”, removing obsolete UI elements and debugging logs, and updating locale strings. Import paths and table configurations are also modified to align with the new data representations.

Changes

File(s) Change Summary
apps/.../controls/[controlId]/components/ArtifactsTable.tsx
apps/.../controls/[controlId]/data/getRelatedArtifacts.ts
Updated artifacts handling: enhanced prop types to include evidence and policy, modified cell rendering, sorting, and filtering, updated row routing based on artifact type, removed transformation logic, and refined error messages.
apps/.../controls/[controlId]/components/RequirementsTable.tsx
apps/.../controls/[controlId]/components/SingleControl.tsx
apps/.../controls/[controlId]/data/getControl.ts
Revised requirements handling: extended types to incorporate frameworkInstance, modified column accessor keys and cell rendering to display framework details, updated sorting, and adjusted query inclusion for framework instance.
apps/.../controls/[controlId]/page.tsx
apps/.../controls/components/controls-table-columns.tsx
Updated configuration: changed the import path to an absolute reference and renamed table headers from “Mapped Requirements” to “Linked Requirements”.
apps/.../evidence/[evidenceId]/components/EvidenceDetails.tsx
apps/.../evidence/[evidenceId]/components/ReviewSection.tsx
apps/.../components/data-table/data-table-sort-list.tsx
UI adjustments: removed an extraneous Alert component from evidence details, made review section header dynamic based on evidence properties, and deleted debugging console logs in the data table sort list.
apps/.../locales/features/controls.ts
apps/.../locales/features/frameworks.ts
Locale updates: revised terminology to “Linked Artifacts/Requirements”, updated messages for no artifacts found, and added new fields (e.g., frameworkId and requirementId) with corresponding labels.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant AT as ArtifactsTable
    participant Router as Router

    U->>AT: Clicks on an artifact row
    AT->>AT: getRowId(row)
    alt row.type is "policy"
       AT->>Router: Navigate to /policies/{policyId}
    else row.type is "evidence"
       AT->>Router: Navigate to /evidence/{evidenceId}
    else
       AT->>Router: Navigate to /artifacts/{id}
    end
Loading

Possibly Related PRs

Poem

I’m a bouncy rabbit with some code to share,
New types and routes now fill the air.
Artifacts, frameworks, neatly aligned,
Hop through the changes, perfectly designed.
Debug logs vanish, UI shines anew –
A rabbit’s cheer for code, so true! 🐰✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 907e4d2 and 809827d.

📒 Files selected for processing (12)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/controls/[controlId]/components/ArtifactsTable.tsx (5 hunks)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/controls/[controlId]/components/RequirementsTable.tsx (5 hunks)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/controls/[controlId]/components/SingleControl.tsx (1 hunks)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/controls/[controlId]/data/getControl.ts (1 hunks)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/controls/[controlId]/data/getRelatedArtifacts.ts (3 hunks)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/controls/[controlId]/page.tsx (1 hunks)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/controls/components/controls-table-columns.tsx (2 hunks)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/evidence/[evidenceId]/components/EvidenceDetails.tsx (0 hunks)
  • apps/app/src/app/[locale]/(app)/(dashboard)/[orgId]/evidence/[evidenceId]/components/ReviewSection.tsx (1 hunks)
  • apps/app/src/components/data-table/data-table-sort-list.tsx (0 hunks)
  • apps/app/src/locales/features/controls.ts (1 hunks)
  • apps/app/src/locales/features/frameworks.ts (4 hunks)
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants