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: reset input fields in API delete dialog after reopening #2316

Merged

Conversation

Vardhaman619
Copy link
Contributor

@Vardhaman619 Vardhaman619 commented Oct 11, 2024

What does this PR do?

This PR fixes the issue where form fields in the "API Delete" dialog do not reset upon reopening. Previously, input values persisted after the dialog was closed and reopened. Now, the form fields are properly reset to their default state when the dialog is opened again.

Fixes #2296

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How should this be tested?

  1. Navigate to Dashboard -> APIs -> Select any API -> API Settings -> Click on Delete API.
  2. Open the Delete API dialog, enter data in the input fields, close the dialog, and then reopen it.
  3. Verify that the input fields are reset to their default (empty) state on reopening.

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read Contributing Guide
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand areas
  • Ran pnpm build
  • Ran pnpm fmt
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Unkey Docs if changes were necessary

Summary by CodeRabbit

  • New Features

    • Enhanced user experience by resetting form fields in the Delete API dialog when closed.
  • Bug Fixes

    • Improved functionality to clear inputs, preventing potential user errors.

Copy link

changeset-bot bot commented Oct 11, 2024

⚠️ No Changeset found

Latest commit: 603215c

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

vercel bot commented Oct 11, 2024

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

Name Status Preview Comments Updated (UTC)
dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 13, 2024 9:34am
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 13, 2024 9:34am
play ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 13, 2024 9:34am
workflows ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 13, 2024 9:34am
www ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 13, 2024 9:34am

Copy link

vercel bot commented Oct 11, 2024

@Vardhaman619 is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Oct 11, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes in this pull request involve the addition of a handleDialogOpenChange function in the DeleteApi component to manage the dialog's open state and reset the form when the dialog is closed. A useEffect hook is introduced to reset the form fields upon changes to the dialog's open state. The import statements for useEffect and useState are updated accordingly. The overall structure of the component remains unchanged.

Changes

File Path Change Summary
apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx Added handleDialogOpenChange function and useEffect hook to reset form fields on dialog state change; updated import statement.

Assessment against linked issues

Objective Addressed Explanation
Reset form fields in API delete dialog (Issue #2296)

Possibly related PRs

  • fix: Delete modal fixes for longer permissions #2084: The changes in the DeletePermission component involve improvements to the dialog's usability, which is conceptually related to the enhancements made in the DeleteApi component's dialog handling and state management.

Suggested reviewers

  • chronark

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

github-actions bot commented Oct 11, 2024

Thank you for following the naming conventions for pull request titles! 🙏

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

🧹 Outside diff range and nitpick comments (1)
apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (1)

87-92: LGTM: Form reset functionality implemented correctly.

The added useEffect hook successfully addresses the issue of form fields not resetting when the dialog is reopened. It correctly triggers the form reset when the dialog is closed, which aligns with the PR objectives.

Consider optimizing the dependency array by using useCallback for form.reset:

const resetForm = useCallback(() => form.reset(), [form]);

useEffect(() => {
  if (!open) {
    resetForm();
  }
}, [open, resetForm]);

This optimization ensures that the resetForm function reference remains stable across renders, potentially reducing unnecessary effect triggers.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 0608fee and 4d3f8cf.

📒 Files selected for processing (1)
  • apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (2 hunks)
🧰 Additional context used
🔇 Additional comments (2)
apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (2)

4-4: LGTM: Import statement updated correctly.

The addition of useEffect to the import statement is appropriate for implementing the form reset functionality, which aligns with the PR objectives.


Line range hint 1-193: Summary: Changes successfully address the PR objectives.

The implemented changes effectively solve the issue of form fields not resetting when the API delete dialog is reopened. The addition of the useEffect hook to reset the form when the dialog closes directly addresses the problem described in the PR objectives and the linked issue.

The changes are minimal, focused, and don't introduce any unrelated modifications to the component. This approach maintains the existing functionality while improving the user experience by ensuring that the form is always in a clean state when opened.

To ensure that these changes don't affect other parts of the codebase, please run the following verification script:

✅ Verification successful

Verification Successful

The verification confirms that the DeleteApi component is used appropriately within the codebase. No other components utilize the open state in a manner that requires similar updates. The changes made effectively address the initial issue without introducing any unintended side effects.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the DeleteApi component is only used in the expected locations and that no other components are using the 'open' state in a similar manner that might need updating.

# Test 1: Check for usage of DeleteApi component
echo "Checking for usage of DeleteApi component:"
rg --type typescript --type typescriptreact "import.*DeleteApi" -g '!delete-api.tsx'

# Test 2: Check for similar patterns that might need updating
echo "Checking for similar patterns that might need updating:"
rg --type typescript --type typescriptreact "useEffect\(.+open.+form\.reset" -g '!delete-api.tsx'

# Note: If these searches return results, they may indicate areas that need similar updates or potential inconsistencies in the codebase.

Length of output: 472


Script:

#!/bin/bash
# Description: Verify that the DeleteApi component is only used in the expected locations and that no other components are using the 'open' state in a similar manner that might need updating.

# Test 1: Check for usage of DeleteApi component excluding delete-api.tsx
echo "Checking for usage of DeleteApi component:"
rg "import.*DeleteApi" -g '*.ts' -g '*.tsx' -g '!delete-api.tsx'

# Test 2: Check for similar useEffect patterns that reset the form based on 'open' state excluding delete-api.tsx
echo "Checking for similar useEffect patterns that might need updating:"
rg "useEffect\(.+open.+form\.reset" -g '*.ts' -g '*.tsx' -g '!delete-api.tsx'

# Note: If these searches return results, they may indicate areas that need similar updates or potential inconsistencies in the codebase.

Length of output: 1463

@ankurjaiswalofficial
Copy link

/assign

Copy link

oss-gg bot commented Oct 11, 2024

Assigned to @ankurjaiswalofficial! Please open a draft PR linking this issue within 48h ⚠️ If we can't detect a PR from you linking this issue in 48h, you'll be unassigned automatically 🕹️ Excited to have you ship this 🚀

@chronark
Copy link
Collaborator

@Vardhaman619 I think useEffect is overkill and makes it more complicated than it needs to be

the modal itself already gives us a way to hook into the close event

<Dialog open={open} onOpenChange={(o) => setOpen(o)}>

Let's use that instead

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: 1

🧹 Outside diff range and nitpick comments (1)
apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (1)

124-124: Approve Dialog component change and suggest cleanup

The onOpenChange prop is correctly set to handleDialogOpenChange, which effectively implements the form reset functionality when the dialog state changes. This change addresses the PR objective and aligns with the suggestion to use the modal's built-in close event hook.

Given that this implementation doesn't use useEffect, please remove any unused useEffect hooks in the component if present.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4d3f8cf and 87b4590.

📒 Files selected for processing (1)
  • apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (3 hunks)
🧰 Additional context used
🔇 Additional comments (2)
apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (2)

Line range hint 1-192: Summary of changes and effectiveness

The implemented changes effectively address the PR objective of resetting input fields in the API delete dialog after reopening. The solution uses a direct approach by leveraging the Dialog component's onOpenChange prop, which is simpler and more maintainable than using a useEffect hook.

Key points:

  1. The handleDialogOpenChange function combines setting the dialog state and resetting the form.
  2. The Dialog component correctly uses this function in its onOpenChange prop.

These changes should resolve the issue of persisting input values when reopening the dialog, improving the user experience as intended.

To ensure completeness:

  1. Verify that there are no unused useEffect hooks in the component.
  2. Consider adding a brief comment explaining the purpose of handleDialogOpenChange for future maintainability.

87-90: Approve new function and verify its usage

The new handleDialogOpenChange function effectively addresses the PR objective by resetting the form when the dialog state changes. This is a good approach to ensure that input fields are cleared when the dialog is reopened.

Please ensure that this function is being used correctly. Run the following script to verify its usage:

✅ Verification successful

Update Shell Script to Verify Usage of handleDialogOpenChange

Please run the following updated script to verify the usage of the handleDialogOpenChange function:


Update Shell Script to Search .ts and .tsx Files Without --type Flags

Please run the following updated script to verify the usage of the handleDialogOpenChange function:


Function handleDialogOpenChange usage verified

The handleDialogOpenChange function is correctly implemented and utilized within delete-api.tsx. It effectively resets the form when the dialog state changes, aligning with the PR objectives.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of handleDialogOpenChange function

# Test: Search for handleDialogOpenChange usage
rg --type typescript 'handleDialogOpenChange' apps/dashboard/app/

Length of output: 100


Script:

#!/bin/bash
# Description: Verify the usage of handleDialogOpenChange function

# Test: Search for handleDialogOpenChange usage
rg 'handleDialogOpenChange' --type ts --type tsx apps/dashboard/app/

Length of output: 96


Script:

#!/bin/bash
# Description: Verify the usage of handleDialogOpenChange function

# Test: Search for handleDialogOpenChange usage in .ts and .tsx files
rg 'handleDialogOpenChange' --glob '*.ts' --glob '*.tsx' apps/dashboard/app/

Length of output: 318

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

🧹 Outside diff range and nitpick comments (1)
apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (1)

22-25: LGTM with suggestion: Import statements reorganized

The separation of import statements improves readability and follows best practices. However, the useEffect import is missing, which might be needed based on the AI summary.

Consider adding the useEffect import if it's used in the component:

-import { useState } from "react";
+import { useEffect, useState } from "react";

Also applies to: 28-29

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 87b4590 and 603215c.

📒 Files selected for processing (1)
  • apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (4 hunks)
🧰 Additional context used
🔇 Additional comments (4)
apps/dashboard/app/(app)/apis/[apiId]/settings/delete-api.tsx (4)

4-5: LGTM: Import statements separated

The separation of import statements for Button and Card components improves readability and follows best practices.


84-88: LGTM: Implemented form reset on dialog state change

The new handleDialogOpenChange function effectively addresses the PR objective by resetting the form when the dialog is closed. This implementation aligns with the feedback to use the modal's close event, providing a simple and effective solution.


121-121: LGTM: Dialog component updated to use new handler

The Dialog component has been correctly updated to use the new handleDialogOpenChange function for its onOpenChange prop. This change ensures that the form reset occurs when the dialog state changes, aligning with the PR objectives.


Line range hint 1-191: Great job: Implemented solution without unnecessary complexity

The changes successfully address the PR objectives without using useEffect, aligning with the feedback provided by chronark. The implementation is simpler and more direct, which is preferable.

To ensure there are no leftover artifacts from previous implementations, please run the following script to check for any unused imports:

If the script returns any results, consider removing the unused imports.

✅ Verification successful

Action Required: Update Shell Script with Correct File Type

The previous shell script failed due to an unrecognized file type typescript. Please update the script to use the correct file type tsx for TypeScript React files.


Action Required: Update Shell Script to Use Glob Pattern for .tsx Files

The --type tsx flag is not recognized by ripgrep. Instead, use a glob pattern to target .tsx files directly.


Verification Complete: No Unused Imports Found

The delete-api.tsx file does not include any unused imports, specifically useEffect. The implementation is clean and aligns with the review objectives.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for unused imports in the file

# Test: Search for unused imports, particularly useEffect
rg --type typescript 'import.*useEffect' apps/dashboard/app/\(app\)/apis/\[apiId\]/settings/delete-api.tsx

Length of output: 141


Script:

#!/bin/bash
# Description: Check for unused imports in the file

# Test: Search for unused imports, particularly useEffect
rg --type tsx 'import.*useEffect' apps/dashboard/app/\(app\)/apis/\[apiId\]/settings/delete-api.tsx

Length of output: 127


Script:

#!/bin/bash
# Description: Check for unused imports in the file

# Test: Search for unused imports, particularly useEffect
rg --glob '*.tsx' 'import.*useEffect' apps/dashboard/app/\(app\)/apis/\[apiId\]/settings/delete-api.tsx

Length of output: 103

@chronark chronark enabled auto-merge October 13, 2024 09:19
Copy link

oss-gg bot commented Oct 13, 2024

Awarding Vardhaman619: 150 points 🕹️ Well done! Check out your new contribution on oss.gg/Vardhaman619

AkshayBandi027 pushed a commit to AkshayBandi027/unkey that referenced this pull request Oct 14, 2024
…#2316)

* fix: reset input fields in API delete dialog after reopening

* refactor: remove unnecessary useEffect and utilize existing onOpenChange function for dialog

* refactor: removed unused imports
AkshayBandi027 pushed a commit to AkshayBandi027/unkey that referenced this pull request Oct 14, 2024
…#2316)

* fix: reset input fields in API delete dialog after reopening

* refactor: remove unnecessary useEffect and utilize existing onOpenChange function for dialog

* refactor: removed unused imports
chronark added a commit that referenced this pull request Oct 28, 2024
* fix:breadcrum-cache-issue

* chore:rename-revalidateMytag

* refactor: move-revalidateTag

* refactor: extract tags into reusable utility

* feat: add template

* Update 3_follow_the_unkey_x_account.md (#2323)

* fix: capture uniqueness error and return it correctly (#2337)

* docs: getVerifications instead of get (#2329)

* Update 3_follow_the_unkey_x_account.md (#2324)

Followed unkey on Twitter

Co-authored-by: Andreas Thomas <dev@chronark.com>

* fix: transaction ...: in use: for query (#2278)

* fix: transaction ...: in use: for query
- Fixes #2197
- The error is caused by the cache revalidation happening in the background, so we have a racecondition with the other queries we are running in the insertGenericAuditLogs function

* docs: explain for future self

* fix: another racecondition
also bulk insert auditLogs and auditLogTargets

* [autofix.ci] apply automated fixes

---------

Co-authored-by: chronark <dev@chronark.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

* fix: handle undefined ratelimits

* Update 3_follow_the_unkey_x_account.md (#2338)

* fix: handle case when blogs array is empty

* [oss.gg] side quest : added another framework; hono on cloudflare workers. (#2345)

* fix: weird spacing in changelog by removing the extra gap (#2340)

* fix: weird spacing in changelog

* feat: formatted

* oss.gg: create a template for ratelimiting a oak server in deno with unkey (#2308)

Co-authored-by: Andreas Thomas <dev@chronark.com>

* follow unkey on X #2252 (#2315)

Co-authored-by: Your Name <you@example.com>

* Follow the Unkey X account: @unkeydev Complete! (#2332)

* Update 3_follow_the_unkey_x_account.md

* Update 3_follow_the_unkey_x_account.md

---------

Co-authored-by: Andreas Thomas <dev@chronark.com>

* fix(www): analytics bento code snippet is not readable (#2311)

- add hover effect to analytics bento removing gradient background
- make copy code button sticky to top-right corner
- impl independent vertical scrolls for language switcher and code editor

* Update 7_create_a_template.md

* Update 7_create_a_template.md

* chore(deps-dev): bump @content-collections/core from 0.6.2 to 0.7.2 (#2255)

Bumps @content-collections/core from 0.6.2 to 0.7.2.

---
updated-dependencies:
- dependency-name: "@content-collections/core"
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* fix: order audit logs by time, show latest on top (#2295)

* feat: add template

* feat: Unkey FastAPI boilerplate (#2307)

* feat: add template

* feat: follow unkey on X (#2357)

* Update 6_record_onboarding.md (#2301)

* fix: reset input fields in API delete dialog after reopening (#2316)

* fix: reset input fields in API delete dialog after reopening

* refactor: remove unnecessary useEffect and utilize existing onOpenChange function for dialog

* refactor: removed unused imports

* Update 3_follow_the_unkey_x_account.md (#2364)

Added name to the followed list.

Co-authored-by: Andreas Thomas <dev@chronark.com>

* ci: add label

* feat: add hover to input fields

* Added gaps and width for md (#2371)

* docs: update overview.mdx (#2384)

avaliable -> available

* oss.gg side quest 3_follow_the_unkey_x_account.md (#2399)

Followed the unkey x account

* feat: Following unkey acc on twitter #2407 (#2408)

* Feat: Followed Unkey on X

* Feat: Followed Unkey on Twitter

---------

Co-authored-by: Andreas Thomas <dev@chronark.com>

* resolve merge conflicts

* resolve merge conflicts

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: chronark <dev@chronark.com>
Co-authored-by: Emily Marie Ahtúnan <86572370+Emmarie-Ahtunan@users.noreply.github.com>
Co-authored-by: Harsh Shrikant Bhat <90265455+harshsbhat@users.noreply.github.com>
Co-authored-by: Aritra Sadhukhan <60315087+aritradevelops@users.noreply.github.com>
Co-authored-by: Flo <53355483+Flo4604@users.noreply.github.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Devang Rakholiya <116096508+Devang0907@users.noreply.github.com>
Co-authored-by: Prabin <42871240+prabincankod@users.noreply.github.com>
Co-authored-by: ZiaCodes <72739794+Khaan25@users.noreply.github.com>
Co-authored-by: Devansh Baghel <77718741+Devansh-Baghel@users.noreply.github.com>
Co-authored-by: Shreenarayan jaiswal <127131074+shreenarayan123@users.noreply.github.com>
Co-authored-by: Your Name <you@example.com>
Co-authored-by: Chirag Arora <chirag8023@gmail.com>
Co-authored-by: Nazar Poshtarenko <32395926+unrenamed@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Saketh Pavan Goti <44170829+Sakethpavan@users.noreply.github.com>
Co-authored-by: Teddy ASSIH <110066080+Ionfinisher@users.noreply.github.com>
Co-authored-by: Vardhaman Bhandari <97441447+Vardhaman619@users.noreply.github.com>
Co-authored-by: Atharva_404 <72994819+Atharva-3000@users.noreply.github.com>
Co-authored-by: Rishi <rishipatel0826@gmail.com>
Co-authored-by: Ikko Eltociear Ashimine <eltociear@gmail.com>
Co-authored-by: Ayan Mondal <ayanmondal1805@gmail.com>
Co-authored-by: Kunal Arya <105645118+kunalarya873@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Form Fields Not Resetting in API Delete Dialog
3 participants