Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: fixed incorect reason of revision #3054

Merged
merged 3 commits into from
Feb 14, 2025
Merged

Conversation

chesterkmr
Copy link
Collaborator

@chesterkmr chesterkmr commented Feb 14, 2025

Summary by CodeRabbit

  • Bug Fixes
    • Adjusted how decision details are presented by now displaying the document’s revision reason instead of a generic status, ensuring that users see more precise and accurate information.
  • Chores
    • Updated version to 0.3.130 in the changelog and package.json.
    • Incremented dependency version for @ballerine/ui from 0.5.76 to 0.5.77.
    • Updated subproject commit reference.

Copy link

changeset-bot bot commented Feb 14, 2025

⚠️ No Changeset found

Latest commit: 0cd2af0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

coderabbitai bot commented Feb 14, 2025

Warning

Rate limit exceeded

@chesterkmr has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 36 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 3f49740 and 0cd2af0.

📒 Files selected for processing (1)
  • apps/kyb-app/src/pages/CollectionFlow/versions/v2/components/organisms/CollectionFlowUI/hooks/usePriorityFields/utils/generate-priority-fields.unit.test.ts (4 hunks)

Walkthrough

The change updates the generatePriorityFields function to extract the document decision reason from document.decision?.revisionReason instead of document.decision?.status. The function continues to process document field definitions and child elements recursively, returning an array of IPriorityField objects or undefined when no priority fields exist. Overall control flow and error handling remain unchanged. Additionally, the versioning of the kyb-app package and its dependencies is updated, and a new entry is added to the changelog.

Changes

File Path Change Summary
apps/kyb-app/src/.../generate-priority-fields.ts Updated the extraction logic to use document.decision?.revisionReason instead of document.decision?.status for the reason.
apps/kyb-app/CHANGELOG.md Added new version entry 0.3.130 with a "Patch Changes" section indicating a "Bump."
apps/kyb-app/package.json Updated package version from 0.3.129 to 0.3.130 and dependency version from @ballerine/ui 0.5.76 to 0.5.77.
services/workflows-service/prisma/data-migrations Updated subproject commit reference from 3ac3af4ab32eb65b2235042d19aac2151c992619 to 648003c22f5f59b2dc88c5e4b940b48b18aacdc8.

Possibly related PRs

  • Illiar/fix/v2 adjustments #3007: The changes in the main PR are related to the modifications made in the generatePriorityFields function in the retrieved PR, as both involve alterations to the same function within the same file.

Suggested reviewers

  • tomer-shvadron

Poem

In lines of code, I hop and play,
A tiny change lights up my day.
From status old to revision bright,
The code now sings in clearer light.
With joyful hops, I celebrate the change—
A rabbit’s cheer, both fun and strange! 🐇✨


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?

❤️ 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. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
apps/kyb-app/src/pages/CollectionFlow/versions/v2/components/organisms/CollectionFlowUI/hooks/usePriorityFields/utils/generate-priority-fields.ts (1)

43-44: Track implementation of priority fields for other elements.

These TODO comments indicate incomplete implementation. Consider creating tracking issues for:

  1. Implementing priority fields extraction from other elements
  2. Defining where revision reasons will be stored for other elements

Would you like me to help create tracking issues for these TODOs?

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 99b484a and 9865ac1.

📒 Files selected for processing (1)
  • apps/kyb-app/src/pages/CollectionFlow/versions/v2/components/organisms/CollectionFlowUI/hooks/usePriorityFields/utils/generate-priority-fields.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: Analyze (javascript)
  • GitHub Check: test_windows
  • GitHub Check: test_linux
  • GitHub Check: build (windows-latest)
  • GitHub Check: lint
  • GitHub Check: build (ubuntu-latest)
🔇 Additional comments (1)
apps/kyb-app/src/pages/CollectionFlow/versions/v2/components/organisms/CollectionFlowUI/hooks/usePriorityFields/utils/generate-priority-fields.ts (1)

33-33:

❓ Verification inconclusive

LGTM! Verify document schema migration.

The change to use revisionReason instead of status is correct as it's more specific for revision purposes.

Let's verify that all documents in the codebase have been updated to use revisionReason:


🏁 Script executed:

#!/bin/bash
# Search for any remaining uses of decision.status in the codebase
rg "decision\?\.status" --type ts

Length of output: 5241


Action Required: Verify Consistent Schema Migration

The update in apps/kyb-app/src/pages/CollectionFlow/versions/v2/components/organisms/CollectionFlowUI/hooks/usePriorityFields/utils/generate-priority-fields.ts correctly extracts the revision reason using document.decision?.revisionReason. However, our search shows that many other files (for example, in apps/kyb-app/src/components/organisms/DynamicUI/Page/hooks/usePageErrors/usePageErrors.ts and several files in the backoffice-v2 and services/workflows-service directories) still reference document.decision?.status. Please review whether these references should be migrated to use revisionReason as well or if they are intentionally left unchanged for backward compatibility. Also, note the TODO comments regarding additional element handling in the same file.

  • File Under Review:
    apps/kyb-app/src/pages/CollectionFlow/versions/v2/components/organisms/CollectionFlowUI/hooks/usePriorityFields/utils/generate-priority-fields.ts — line 33 update from status to revisionReason

  • Additional References to Check:

    • apps/kyb-app/src/components/organisms/DynamicUI/Page/hooks/usePageErrors/usePageErrors.ts
    • Files in backoffice-v2 (e.g., useCaseDecision.tsx, usePendingRevisionEvents/utils/calculate-pending-workflow-events.ts, etc.)
    • Common utilities in packages/common/src/utils
    • Workflow services in services/workflows-service

Please ensure that the document schema migration is consistent across the codebase or that any deviations are intentional.

@chesterkmr chesterkmr enabled auto-merge (squash) February 14, 2025 10:56
@chesterkmr chesterkmr merged commit 686df12 into dev Feb 14, 2025
18 checks passed
@chesterkmr chesterkmr deleted the illiar/fix/revision-reason branch February 14, 2025 11:23
chesterkmr added a commit that referenced this pull request Feb 14, 2025
* Dev 336/amplify webhook builds (#2906)

* feat: added new actions to build front-end apps manually

* fix: fixed a typo

* fix: changed the action names for the new front-end build actions

* feat: added on-failuew job to notify when the job fails

* fix: added changes code rabbit

* fix: removed redundant step for build action

* chore: removing on push trigger on the actions

* [bal-3442] - Backoffice - Display timestamp in local timezone for transaction monitoring (#3037)

* fix(transaction.mapper): remove unnecessary success log on validation (#3023)

- Eliminate console.log for successful validation
- Clean up the code for improved readability

(your logs are so verbose, they could be mistaken for a motivational speech)

* feat(docs): add development rules for backoffice-v2, kyb-app, workflows-dashboard (#3038)

* feat(docs): add development rules for backoffice-v2, kyb-app, workflows-dashboard

- Introduce best practices for React TypeScript development
- Include guidance on components, hooks, state management, and testing

(These rules are so thorough, they could double as a user manual for a space shuttle)

* docs(workflows): enhance workflow service rules and guidelines

- Expand code organization and structure guidelines
- Introduce TypeScript usage best practices
- Include detailed documentation on error handling and API design

(Your code organization is so messy, it makes a cluttered desk look like a minimalist art piece)

* chore: run dist with environment variables (#2643) (#3041)

* chore: run dist with environment variables (#2643)

* fix: adding trimmer in end of env name

---------

Co-authored-by: ChiragSharma <[email protected]>
Co-authored-by: Alon Peretz <[email protected]>

* refactor(EditableDetails): optimize form handling with useMemo (#3048)

- Replace direct defaultValues assignment with memoized formValues
- Remove unnecessary useEffect for form reset on data change
- Simplify conditional rendering logic in the return statement

Co-authored-by: Alon Peretz <[email protected]>

* refactor(components): streamline details component properties access (#3049)

- Remove optional chaining for value.id and value.title
- Improve readability by ensuring direct property access

refactor(hooks): add workflowId to bankAccount and credit check blocks

- Update hooks to receive workflowId for better context handling
- Simplify conditional checks for plugin outputs

chore(migrations): update subproject commit reference

- Sync submodule to latest commit in workflows-service

* Use `report_outcomes` for report display (#3035)

* fix: table page

* wip

* fix: formating

* wip

* fix: small fixes

* fix

* fix: ui bug

* build: new version

* fix: validate report metadata

* fix: pr comments

* fix: pnpm-lock.json

* fix: update package

* fix: update package

* fix: update package

* fix: update package

* fix: update package

* fix: update package

* feat(bal-3616): added demo account config option (#3046)

* feat(bal-3616): added demo account config option

* chore: pr review fixes

* Illiar/feat/common document schemas (#3051)

* feat: added pci-certification document

* feat: added financial document && bump

* fix: lock fix

* fix: fixed backoffice crash & ui bump (#3053)

* fix: fixed incorect reason of revision (#3054)

---------

Co-authored-by: Chirag <[email protected]>
Co-authored-by: liorzam <[email protected]>
Co-authored-by: Alon Peretz <[email protected]>
Co-authored-by: pratapalakshmi <[email protected]>
Co-authored-by: ChiragSharma <[email protected]>
Co-authored-by: Shane <[email protected]>
Co-authored-by: Tomer Shvadron <[email protected]>
Co-authored-by: Matan Yadaev <[email protected]>
Co-authored-by: Artem Lavrentii <[email protected]>
Co-authored-by: Illia Rudniev <[email protected]>
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