I've created a module which consists of a form that should only allows submissions if certain fields required fields are present. As expected, when editing and testing the module in isolation, the submission button is disabled until those fields are filled out. However, when I use the module in an app, the submission button remains active and usable even though the fields required by the validation are still empty.
I'm using a form and using the Disable Submit
option with Custom Rules: something like {{ newNameInput.invalid || !tsformIsValid.value }}
where newNameInput
is a form field and tsformIsValid
is a transformer defined in the same module that returns error strings based on the form fields.
When I inspect the module state in the app, the transformer validation does indicate that the validation rules are not met.
I've published updated versions of the module to make sure the app has the most recent changes.
Based on this post I've tried renaming my form validation transformer to avoid namespace collision with a different transformer in the app, but no dice.
-
Screenshot of the module sandbox with the "Rename" submission button disabled as expected
-
The same module within an app. The "Rename" submission button is enabled and triggers a query.
I'm scratching my head at why the validation defined in the module is ignored in the app. Any ideas?