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

[Content Manager] Uniqueness checking not simultaneous #20600

Open
MarionLemaire opened this issue Jun 21, 2024 · 0 comments
Open

[Content Manager] Uniqueness checking not simultaneous #20600

MarionLemaire opened this issue Jun 21, 2024 · 0 comments
Labels
issue: bug Issue reporting a bug severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package version: 5

Comments

@MarionLemaire
Copy link
Contributor

Bug report

Required System information

Node.js version: 20.9.0
Strapi version: 5.0.0-beta.13
Operating system: Windows WSL and OS

Describe the bug

Text, Number and Email fields uniqueness is checked, then Date field uniqueness is checked : it should be simultaneous

Steps to reproduce the behavior

  1. Create a CT with 4 types of Unique fields : Text, Number, Email and Date.
  2. Go to CM, fill in an entry with all fields.
  3. Fill in a second entry with the exact same data and Save
  4. Check that only Text, Number and Email fields are considered as errors
  5. Update the Text, Number and Email fieds, and Save
  6. Check that now, Date field is also considered as error
  7. Update Date and Save: it works

Expected behavior

All uniquess checking should be made at the same time.

Screenshots

https://app.dashcam.io/replay/667416812ec76900760d9d54?share=lIia3HAaJZ4ymSEvOVQCIg

@hanpaine hanpaine added issue: bug Issue reporting a bug severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package labels Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Issue reporting a bug severity: low If the issue only affects a very niche base of users and an easily implemented workaround can solve source: core:content-manager Source is core/content-manager package version: 5
Projects
Status: To be reviewed
Status: Backlog
Status: To review
Development

No branches or pull requests

2 participants