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

Unintended rewrite of field handle #1249

Closed
ReneWeCode opened this issue Jan 23, 2020 · 3 comments
Closed

Unintended rewrite of field handle #1249

ReneWeCode opened this issue Jan 23, 2020 · 3 comments

Comments

@ReneWeCode
Copy link
Contributor

When you reopen a newly created field, the handler is rewritten back to if it wasn't set.

This happens before the field is saved.

handle-rewrite

@andjsch
Copy link
Contributor

andjsch commented May 4, 2020

This is one annoying bug. Just writing this comment in the hopes that this one get's a higher priority.

I am used to look up the handles after being done with creating the blueprints. This keeps me looking in the files directly, which is not that convenient in my current workflow.

@miclf
Copy link

miclf commented Aug 7, 2020

I’ve encountered the same issue. Screenshot:

foo

The second field here (handle) has the correct value in the YAML file of the blueprint. But that value is not loaded here (or it is immediately overwritten by this automatic slug thing). If I save the config as is, the YAML file then gets the new, incorrect value.

So, if we’re not careful to manually rewrite the handle every time we update the field config, the handle gets wrongly modified and then everything breaks.

@jesseleite
Copy link
Member

Just a note (worked this out with @miclf in Discord) that it doesn't happen on a saved blueprint field, only when creating a new field.

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

No branches or pull requests

5 participants