Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Prevent field collisions #17

Open
jacobwegner opened this issue Dec 3, 2015 · 0 comments
Open

Prevent field collisions #17

jacobwegner opened this issue Dec 3, 2015 · 0 comments
Assignees
@jacobwegner

Comments

@jacobwegner
Copy link
Contributor

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
@jacobwegner jacobwegner self-assigned this Dec 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jacobwegner jacobwegner

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jacobwegner