Fix the 'AddLinkedUser' dialog from configuration Page

[mit-27]

Problems to be fixed by this PR

• The new LinkedUser was added by clicking the Cancel button of 'AddLinkedUser' dialog on the Configuration Page
• The form displays the old value of the orgin-identifier from a previously submitted form.

Summary by CodeRabbit

• New Features
  • Enhanced the user experience in the configuration settings by allowing linked accounts to be added more seamlessly.
• Bug Fixes
  • Fixed an issue where the form fields were not resetting after submission.
• Refactor
  • Improved form handling in the configuration settings for better user interaction.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f863aeb

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

This update enhances the user experience in the AddLinkedAccount component of a web application. It ensures that after a user submits a form, the form is reset, making it ready for another input. Additionally, the update improves the user interface by allowing the "Cancel" button not only to close the dialog but also to reset the form, ensuring a smoother interaction.

Changes

File Path	Changes
.../src/components/configuration/components/AddLinkedAccount.tsx	- Added whitespace - Added form.reset() after form submission - Included form props in <Form> component - Updated onClick for "Cancel" button to reset form and close dialog

Poem

In the field of green, under the bright light's sheen,
Chiefs and 49ers clash, in a Super Bowl bash.
🏈 Amidst the cheers and playful fight,
A rabbit hops in sheer delight.
For every pass and touchdown made,
In the spirit of the game, friendships won't fade.
Let's celebrate each goal, for in this bowl, joy is the ultimate role.

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[ghost]

👇 Click on the image for a new way to code review

Legend

[coderabbitai]

Review Status

Actionable comments generated: 2

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between dc91abe and f863aeb.

Files selected for processing (1)

• apps/webapp/src/components/configuration/components/AddLinkedAccount.tsx (4 hunks)

Additional comments: 2

apps/webapp/src/components/configuration/components/AddLinkedAccount.tsx (2)

• 94-94: Correct use of form.reset() to clear form fields after submission, addressing the UI glitch issue.
• 166-166: Passing form props to the <Form> component is a good practice for form state management, enhancing maintainability and modularity.

[coderabbitai]

Added whitespace is unnecessary and does not contribute to code clarity or functionality.

-    
+

---

Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.

Suggested change

[coderabbitai]

The onClick handler for the "Cancel" button correctly resets the form and closes the dialog, addressing the functionality bug. However, consider separating concerns by creating a dedicated function for this logic.

- onClick={() => {form.reset();setShowNewLinkedUserDialog({open: false})}}
+ onClick={handleCancel}

And then define handleCancel function:

function handleCancel() {
  form.reset();
  setShowNewLinkedUserDialog({open: false});
}