Cina Saffary
Cina Saffary
You need to change the `INPUT_SELECTOR` the plugin uses to determine what types of fields to check. By default, it excludes `[type="hidden"]` fields. ```js $.fn.validator.Constructor.INPUT_SELECTOR = ':input:not([type="submit"], [type="reset"], button)' ```
Are you using the `$().validator('update')` method after disabling or enabling a radio button?
Gonna add support for returning a `$.Deferred`/`Promise` from a validator soon.
Still on the backlog. Haven't thought of a clean way to implement it yet.
I would set `.attr('data-validate', false)` and call `.validator('update')` instead of setting `disabled`.
Can't you make the Cancel button a ``? It won't be disabled then.
:+1: The lack of namespaced events is causing datepicker events to trigger the event handlers of a parent container component (e.g. modals, collapse elements, etc.)
IMO, we should rework the action to use `latest` as a last resort default (rather than some hardcoded version number that'll quickly fall out of date), with the following precedence...
> @petebacondarwin @1000hz to confirm, there is a way around this? a user can specify the version in their package.json? just trying to understand the urgency here Yes, I believe...
It seems like this could be a result of `pnpm` not being available in the runner environment. Are you including https://github.com/pnpm/action-setup in an earlier step of your workflow before `wrangler-action`?