Skip to content

Comments

Fix tabs conflicts in CollectionField when using "useEntryCrudForm"#6464

Open
ggabrovski wants to merge 1 commit intoEasyCorp:4.xfrom
ggabrovski:fix_tab_conflict_collection_field
Open

Fix tabs conflicts in CollectionField when using "useEntryCrudForm"#6464
ggabrovski wants to merge 1 commit intoEasyCorp:4.xfrom
ggabrovski:fix_tab_conflict_collection_field

Conversation

@ggabrovski
Copy link
Contributor

Fix tabs conflicts in CollectionField when using "useEntryCrudForm" with tabs.
See #5690

@javiereguiluz
Copy link
Collaborator

Let's see if we can fix this without using an Ulid in the tab ID. This ID is visible in the URL and the Ulid would make it very long and a bit ugly. Let's try to find an alternative solution. Thanks.

@Seb33300
Copy link
Contributor

Also, FieldDto already has a $uniqueId property with an Ulid. But that property is internal.
If we finally decide to use an Ulid, we may decide to change this so we can reuse that one.

@idmarinas
Copy link

What about the option of adding a prefix/suffix to the ID, from Fields itself, just as you can add propertySuffix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants