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

Grammar fields names issues #18

Closed
Bernardo-MG opened this issue Mar 5, 2015 · 1 comment
Closed

Grammar fields names issues #18

Bernardo-MG opened this issue Mar 5, 2015 · 1 comment
Assignees
Labels

Comments

@Bernardo-MG
Copy link
Collaborator

There is a problem with grammar fields where sometimes it gives the base field name instead of the one of the current field.

For example, after creating a numeric field, and naming it 'Field 1', it's name may still be 'Numeric Field'. This seems to be a problem related with fields being a combination of optional rules.

The easiest way to solve this is to add a 'name' parameter to the field creation methods.

@Bernardo-MG Bernardo-MG added the bug label Mar 5, 2015
@Bernardo-MG Bernardo-MG self-assigned this Mar 9, 2015
@Bernardo-MG Bernardo-MG added this to the Model Parser milestone Mar 12, 2015
@Bernardo-MG
Copy link
Collaborator Author

The factory now makes sure the name is correctly set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant