AutoForm.getInputValue returns wrong result for boolean fields with type='boolean-radios' #474
Labels
Comments
|
Fixed in next release. boolean-select doesn't have the issue. |
aramk
added a commit
to aramk/meteor-autoform
that referenced
this issue
Dec 13, 2014
* commit '44769ca5eafc26ac45799fa4cdaf50956b8f00fd': (21 commits) bump version clarify security (closes Meteor-Community-Packages#520) autosave contenteditable inputs (closes Meteor-Community-Packages#494) Bugfix: if type of keys is Number fixes to selectOptions merge Feature suggest: autoform.options from hashtable bump version fix Meteor-Community-Packages#474 bootstrap-radios values array field style fix fix Meteor-Community-Packages#504 suggest values for afFieldValueContains Fix multi-select issue where we were determining selection status based on 'opt' value (which is at the group level) instead of the actual option ('subOpt'). Multi-select 'selected' now works. fixes issue Meteor-Community-Packages#497 allow providing an onSuccess result from onSubmit (fixes Meteor-Community-Packages#479) set this.docId for insert form onSuccess, too workaround for resetting update forms; fixes to hot code push migration clarify before hooks a bit (Meteor-Community-Packages#477) list add on packages available from others If value invalid return unmodified value, not null Check if view isn't destroyed ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AutoForm.getInputValuereturns the wrong result if anafFieldInputfor a boolean field usestype="boolean-radios".It looks like it's using the value converter for a checkbox even though the field is a radio. I suspect this might also be trouble for
boolean-selectfields -- but I haven't checked that.The text was updated successfully, but these errors were encountered: