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

refactor(Validation): rename FromlyMessage to FormlyValidationMessage #196

Merged
merged 2 commits into from
Oct 29, 2016
Merged

refactor(Validation): rename FromlyMessage to FormlyValidationMessage #196

merged 2 commits into from
Oct 29, 2016

Conversation

aitboudad
Copy link
Member

No description provided.

@mohammedzamakhan
Copy link
Contributor

I was wondering if FormlyValidationMessage should be a in components folder or templates folder. I think it should be in templates because other templates might not need a div, they might want to use a span with some classes or something.

@aitboudad
Copy link
Member Author

let's keep it in components folder, the extra div is removed now

template: `{{errorMessage}}`,

@mohammedzamakhan
Copy link
Contributor

Also think about this, some projects might want to show all the messages to the user, right now our component only shows one. This is definitely a part of template folder since even angular-formly had it in templates.

@aitboudad
Copy link
Member Author

make sense now 👍 , done!

@mohammedzamakhan mohammedzamakhan merged commit ab6b013 into ngx-formly:master Oct 29, 2016
@aitboudad aitboudad deleted the formly-message branch October 29, 2016 14:55
@aitboudad aitboudad mentioned this pull request Oct 29, 2016
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants