Can't Reload Data for "Select" Fields

[gizmoboy]

We have a use-case where we need to reload the saved form data back into a form.

Based on a suggestion from kentcdodds, we are loading the saved datagram back into FormData when reconsituting the form like so:

$scope.formData = {
  firstName: 'Kent C.',
  lastName: 'Dodds'
};
$scope.formFields = [
  {
    key: 'firstName',
    type: 'text'
  },
  {
    key: 'lastName',
    type: 'text'
  }
];

This works great for most field types, but fails for select fields.

It would be very useful to be able to pre- and re-select the appropriate values for select items by passing in the matching object from their options array.

It would be even more flexible to allow value/default selection by name or value of the options array objects, perhaps via some kind of options overload. (e.g. { selectedValue: "foo", propertyName: "name" }

[gizmoboy]

Note: We have abandoned the use of "default" properties altogether and just pass in a (sparsely) populated datagram which is fed into formData upon loading; this serves the same function and actually simplifies the formly json considerably.

[kentcdodds]

I would say +1 on not using "default". May consider removing that @Astrism... People should just load the formlyData with the default values in my opinion.

[ghelton]

I could get behind that change

[gizmoboy]

It's still have an issue in that this default-loading doesn't work for "select" field types. That's more a bug than a drawback to this approach, however.

[gizmoboy]

Would a higher bounty help to get this resolved quicker? It's something holding up a project and my developer is rolling off on friday.

[kentcdodds]

I was looking into it and found that it was a little simpler than I had originally supposed, so I fixed the demo example and removed the default option. You should be able to setup the form data for a select. Let me know if you have trouble.

[gizmoboy]

We're seeing some unusual behavior after this fix; we're passing in name and value for our selects, and values seem to be getting replaced with ordinal numbers. Is there a demo of how we should be setting the starting value? Perhaps we're "holding it wrong."

[kentcdodds]

I'm not sure how that could be happening. If you could make a jsbin to
reproduce the issue, then I could help more.

• Kent C. Dodds
  Sent from my mobile device, please forgive any errors or brevity. (I may
  have used speech to text...)
  On Aug 29, 2014 4:00 PM, "gizmoboy" notifications@github.com wrote:

We're seeing some unusual behavior after this fix; we're passing in name
and value for our selects, and values seem to be getting replaced with
ordinal numbers. Is there a demo of how we should be setting the starting
value? Perhaps we're "holding it wrong."

—
Reply to this email directly or view it on GitHub
https://github.com/nimbly/angular-formly/issues/71#issuecomment-53935006
.