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.

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

Fields with same names but new types should be placed in the original position #2292

Closed
wants to merge 1 commit into from

Conversation

aquajach
Copy link
Contributor

@aquajach aquajach commented May 8, 2015

Fields, with the same names but different types shouldn't always be put at the bottom.

For example, I have a couple fields in the middle of my form, :state and :state_updated_at as a pair of related fields. :state has a type as :string by default, but I would like to make it as :enum. Configuring the :state field will separate two fields and make :state appear at the bottom.

Fields, with the same names but different types shouldn't always be put at the bottom. 

For example, I have a couple fields in the middle of my form, :state and :state_updated_at as a pair of related fields. :state has a type as :string by default, but I would like to make it as :enum. Configuring the :state field will separate two fields and make :state appear at the bottom.
@mshibuya
Copy link
Member

Spec needed!

@mshibuya
Copy link
Member

Closed by #2409.

@mshibuya mshibuya closed this Sep 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants