We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In the two addon wrappers, the templateOptions are provided in the first argument to the resulting onClick handler. https://github.com/ngx-formly/ngx-formly/search?q=FormlyWrapperAddons+extends+fieldwrapper
The templateOptions can be derived from the second argument in the onClick handler (field.to).
Was the intend to provide the addon templateOptions context in the first argument to the resulting onClick handler ?
addonRightClick($event: any) { if (this.to.addonRight.onClick) { this.to.addonRight.onClick(this.to, this, $event); -> this.to.addonRight instead of this.to } } addonLeftClick($event: any) { if (this.to.addonLeft.onClick) { this.to.addonLeft.onClick(this.to, this, $event); -> this.to.addonLeft instead of this.to } }
The text was updated successfully, but these errors were encountered:
add-on::onClick
feat(bootstrap): change add-on::onClick callback signature
6f0d060
BREAKING CHANGE: The two first argument of `onClick` handler has been replaced by `field` instance fix #2617
f063d2b
Successfully merging a pull request may close this issue.
In the two addon wrappers, the templateOptions are provided in the first argument to the resulting onClick handler.
https://github.com/ngx-formly/ngx-formly/search?q=FormlyWrapperAddons+extends+fieldwrapper
The templateOptions can be derived from the second argument in the onClick handler (field.to).
Was the intend to provide the addon templateOptions context in the first argument to the resulting onClick handler ?
The text was updated successfully, but these errors were encountered: