AutoForm does not correctly validate fields with initial value

[abuddenb]

Hello there,

I'm trying to pass data to hidden fields in an AutoForm by setting the value prop:

<AutoField name="graphics_title" value="somestring" />

These fields fail validation until they're manually changed. What am I doing wrong?

[radekmie]

Actually, it's not implemented right now to do so - initial values are taken from your schema. It seems reasonable, to cover your case - given value (if it's present on the first render) should be treated as initial. I'll do it later today.

[radekmie]

Also, you've mentioned hidden fields... It would be great, to add dedicated component to achieve it. I'm curious, how you deal with those. Would you like to create another issue for that?

[abuddenb]

I did this:

const Hidden = props =>
    <input type="hidden" name={props.name} value={props.value} onChange={event => props.onChange(event.target.value)}/>;

const HiddenField = connectField(Hidden, {
    baseField: BaseField,
    initialValue: true
});

[radekmie]

Okay. How about a really hidden field? By really I mean invisible - type="hidden". Also with an option to switch to noDOM mode. Would you like to create another issue? I can also do it by myself.

[abuddenb]

Done: #53.

I'm new to React from Meteor. When you implement initial values, will it matter if the initial value comes from a reactive collection? Ex:

<HiddenField name="graphics_id" value={this.context.graphic._id? this.context.graphic._id : ''}/>

this.context.graphic._id will be an empty string when the page first loads.

[radekmie]

Yes, it will matter - initial values are calling onChange only after their first render.

[abuddenb]

So will onChange detect the updated initial value?

[radekmie]

No. If it will change, it won't be initial value at that time. You have to either wait with render or (what you probably want), use upcoming HiddenField, that will automatically call onChange, when its value will change.

[serkandurusoy]

changing the "visibility" of a field or its container using css causes some
browsers to completely ignore that field!

that's why there is a type=hidden in the html spec.

On Tue, Jun 28, 2016 at 10:56 PM, Radosław Miernik <notifications@github.com

wrote:

Closed #52 #52 via 955f18d
955f18d
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#52 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AEbz3O7oa2q_1R-uoARoC1qwyL4t0uirks5qQXx8gaJpZM4JAaAq
.