Jason Varga

To make this easier to review, I'd stop adding items to the scope of this PR. Additional UI issues can be fixed in separate PRs. If/when you're done with the...

Something just feels odd about seeing a "display" field and then a separate "hide display" toggle. Not to mention all the `hide_display: false`s you'd start getting in your blueprint files....

Yeah that happens now, but we can change how things work.

How about if you have `display: false` it hides the label. A completely missing `display` key will use the fallback behavior we currently have. In the YAML that would be...

I don't want a toggle though. I just want it to work that if you empty the field, it saves `false`.

Can you be more specific with your problem? Which tag is giving your an issue?

I understand that, but which tag are you using? A custom one?

Yep, absolutely a good idea. However it should be an option, not a requirement.

Yeah I _think_ that'll work. Just gotta be aware of how it works if the keys are _missing_ from the `tables` array. Existing users will not have them. ```php 'tables'...

Looks like this is a valid problem, but at the moment we don't support having multiple conditions targeting the same field.