Report view

[Omri-Levy]

• feat(backoffice-v2): added navlink and route for merchant monitoring (Added merchant monitoring route #2394)
• feat(backoffice-v2): added initial table with mocks - made generic no x and pagination components (Added merchant monitoring table #2397)
• Reports view backend integration (Reports view backend integration #2408)
• Reports view create report (Reports view create report #2424)
• feat(*): added route and link to a single report and added report id
• feat(backoffice-v2): added report view shell
• revert(backoffice-v2): reverted severity change from moderate to medium
• Report view shell (Report view shell #2428)
• feat(backoffice-v2): mocked report summary
• fix(backoffice-v2): readded card header x padding
• feat(backoffice-v2): mocked all tabs of report view
• feat(*): integrated report view shell with backend
• feat(backoffice-v2): connected "view" links to tabs
• feat(backoffice-v2): mapped risk levels, summary, and recommendations
• feat(backoffice-v2): mapped risk indicators to data
• feat(*): checkpoint
• feat(backoffice-v2): no longer using mocks for company reputation analysis
• refactor(backoffice-v2): removed mcc related properties as they don't exist as of writing
• feat(backoffice-v2): added skeleton cards for website credibility
• feat(backoffice-v2): now passing real data to ecosystem table
• feat(backoffice-v2): connected all report ui to real data minus website credibility
• feat(backoffice-v2): added adapters, connected missing ui to real data
• feat(*): made merchant monitoring feature flagged
• feat(backoffice-v2): added conditions to start analyzing
• feat(backoffice-v2): populated missing data into report tabs

[changeset-bot]

⚠️ No Changeset found

Latest commit: ff15e57

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

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

[tomer-shvadron]