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

Enforce unique schedule names #1032

Closed
MinhxNguyen7 opened this issue Nov 12, 2024 · 0 comments · Fixed by #1048 · May be fixed by #1049
Closed

Enforce unique schedule names #1032

MinhxNguyen7 opened this issue Nov 12, 2024 · 0 comments · Fixed by #1048 · May be fixed by #1049
Assignees
Labels
enhancement Improvements to the user experience good first task Good task for someone new to the project high High priority issue

Comments

@MinhxNguyen7
Copy link
Member

Description

  • A user should not be able to save their data with duplicate schedule names.
  • They should be prevented from creating a schedule with the same name. If they attempt to save, and there is a duplicate schedule, we can add (NUMBER) to the end of the name before sending it to the backend.
  • Previously, duplicate names were OK because we stored everything as a JSON object in DynamoDB. Now, each schedule is a row in the table, and they would not be distinguishable if they had the same name.

Related Issues

  • Migrate to RDS #970 will mangle schedule names as specified above if that's not done on the frontend.
@MinhxNguyen7 MinhxNguyen7 added enhancement Improvements to the user experience good first task Good task for someone new to the project high High priority issue labels Nov 12, 2024
@github-project-automation github-project-automation bot moved this to Backlog 🥱 in AntAlmanac Nov 12, 2024
@MinhxNguyen7 MinhxNguyen7 moved this from Backlog 🥱 to Onboarding Slate in AntAlmanac Nov 12, 2024
@jotalis jotalis linked a pull request Nov 24, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from In Progress 🤠 to Done 🤩 in AntAlmanac Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvements to the user experience good first task Good task for someone new to the project high High priority issue
Projects
Status: Done 🤩
Development

Successfully merging a pull request may close this issue.

2 participants