Component unique fields

[jhoward1994]

What does it do?

Re implements component unique fields in V5

According to the logic:

• Component unique fields are validated against values in other entries of their parent content type in the same dimensions (locale and publication state)
• All unique values in a repeatable must be unique in the current entity
• The order of components in a repeatable does not matter. Validation will fail if any other entry (of content type + dimensions) holds the same value in the same component field anywhere in the repeatable

Why is it needed?

Fix existing V4 bugs and implement core v5 functionality

How to test it?

API tests
E2E tests

Related issue(s)/PR(s)

DX-1348

WIP

• E2E tests
• Update types for new CTs in API tests
• Add repeatable cases to E2E

closes #12541
closes #12248
closes #10107
closes #17604
closes #16918

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
contributor-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 18, 2024 11:15am

[jhoward1994]

Hey @innerdvations & @Bassel17 the WIPs are complete now so this is ready for review 🙏🏻

[innerdvations]

Overall looks great! Just a few small comments

[innerdvations]

And API tests are failing, but that may be the issue on v5/main. Once we know they're fixed we can run them again.

[jhoward1994]

Known issue with dynamic zones tracked here #20546

ab8e36f - Sets up the correct component context for dynamic zone fields but more work will be required to fix this bug at the query layer

[jhoward1994]

This PR fixes the following issues in Strapi v5

closes #12541
closes #12248
closes #10107
closes #17604
closes #16918