Skip to content

Conversation

@splitbrain
Copy link
Member

We were applying replacements in setVal() but that is weirdly called during parsing and then gets cached. But it's also called again when the validation fails... It's all a mess.

This tries to work around the issue, but I am far from sure this hits all the (edge) cases.

Really without a refactoring of bureaucracy it's nearly impossible to interface cleanly with it.

This applies on top of the multival branch fixes.

We were applying replacements in setVal() but that is weirdly called
during parsing and then gets cached. But it's also called again when the
validation fails... It's all a mess.

This tries to work around the issue, but I am far from sure this hits
all the (edge) cases.

Really without a refactoring of bureaucracy it's nearly impossible
to interface cleanly with it.
@splitbrain splitbrain closed this Jul 24, 2025
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.

2 participants