Skip to content

Prevent field collisions #17

Description

@jacobwegner

Currently, formly uses Field.name to construct dynamic fields on PageForm (and also to add field targets).

If a form has two identically named fields (or two identically named follow-on fields), all sorts of problems come up:

  • only the last-instantiated field is displayed to the user
  • only the last-instantiated follow on is displayed to the user
  • the POSTED data may be validated or saved to the wrong field

I noticed this while investigating #16

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions