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

Why do the fieldLayouts UIDs change so much? #846

Closed
tremby opened this issue Feb 10, 2024 · 2 comments
Closed

Why do the fieldLayouts UIDs change so much? #846

tremby opened this issue Feb 10, 2024 · 2 comments

Comments

@tremby
Copy link

tremby commented Feb 10, 2024

What question would you like to ask?

I've noticed in code review that we sometimes get conflicts on the UID (they look like UIDs at least) keys under fieldLayouts in config/project/neoBlockTypes/*.yaml files. As far as I can tell, neither of the two UIDs in my conflict-marked file correspond to anything in any other yaml file or any filename. Maybe they correspond to something in the database? I never know what to do in this situation, and I tend to cross my fingers and guess, and so far nothing has gone horribly wrong.

I'm not sure exactly when it changes. It seems to change if I save the neo field after somebody else has edited it. It doesn't seem to change again if I then edit it again myself.

Why does it change? How can I know which value is correct? Is this a bug? Can it be made stable?

@ttempleton
Copy link
Contributor

This is definitely a bug. Looking into it now.

@ttempleton
Copy link
Contributor

Thanks for reporting this one as well. It's now fixed for the next release, which will be early next week (hoping to close #842 and #813 first).

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

No branches or pull requests

2 participants