bug/fix_select_rending

[Blokh]

fix: added key for re-rending over value change

Summary by CodeRabbit

• New Features

  • Introduced a new dropdown Select component for enhanced form input options.
  • Improved handling of date-time and date fields to ensure data integrity.
  • Enhanced input type determination for a better user experience.

• Bug Fixes

  • Resolved issues with form resetting when data changes to maintain accuracy.

• Improvements

  • Refined display logic for decision components to align visuals with data logic.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4bdd6e8

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]

Walkthrough

The changes made to the EditableDetails.tsx component focus on enhancing form input handling and logic. A new Select component has been introduced, conditionally rendered based on input type and editability. The onSubmit function has been improved for better handling of date-time fields, ensuring that empty dates are not submitted incorrectly. The getInputType function has been refined for accurate input type determination. Additionally, the Detail component's display logic has been updated, and the form resets when data changes, improving overall functionality and user experience.

Changes

File Path	Change Summary
apps/backoffice-v2/src/lib/blocks/components/EditableDetails/EditableDetails.tsx	- Added new method useInitialCategorySetValue. - Updated EditableDetails method signature. - Modified IDetailProps interface implementation. - Enhanced form input handling with a new Select component. - Improved onSubmit function for date-time handling. - Refined getInputType function for accurate input types. - Updated Detail component display logic. - Implemented form reset on data changes.

Poem

In the fields where details play,
A dropdown blooms, bright as day.
With dates that dance and inputs clear,
The forms now sing, no need to fear.
A rabbit's joy, in code we trust,
For every change, a leap is a must! 🐇✨

---

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>, 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 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 5448ecd and 6f5d9f0.

📒 Files selected for processing (1)

• apps/backoffice-v2/src/lib/blocks/components/EditableDetails/EditableDetails.tsx (1 hunks)

🧰 Additional context used

[coderabbitai]

⚠️ Potential issue

Avoid changing the component's key based on field.value

Assigning a dynamic key that depends on field.value causes the Select component to unmount and remount whenever the value changes. This can lead to loss of internal state and can negatively impact performance. Instead of modifying the key, consider managing the re-rendering through state updates or using useEffect to handle changes.