Skip to content
This repository has been archived by the owner on Nov 6, 2024. It is now read-only.

Update readme "Why ng2-materialize?" section #218

Merged
merged 5 commits into from
Nov 2, 2017
Merged

Conversation

scote
Copy link
Contributor

@scote scote commented Oct 6, 2017

No description provided.

@jfcere jfcere added this to the 1.7.0 milestone Oct 30, 2017
@jfcere jfcere self-requested a review October 31, 2017 01:51
README.md Outdated

We already know the possibilities Materialize offers. What is left to do is to wrap components that we want to use in Angular component.
### Initialization simplified
Copy link
Contributor

@jfcere jfcere Oct 31, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think its a bit heavy for a read-me file (TLDR) ... what do you think about only mentioning those with bullet points? Something like ...

In other words, we ...

  • Simplify components initialization
  • Handle Angular "quirks" with Materialize library
  • Offer component injection when possible
  • Provide a MediaService that allow customization according to view port size
  • Added support for ReactiveForm with validation

Copy link
Contributor Author

@scote scote Oct 31, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty good and it's a good resume to what we try to do.

README.md Outdated
Another nice advantage that we added to our implementation is the Form Validation. Materialize only provide HTML5 validation while we added support for Reactive Form allowing a more flexible way to do form validation following the same Material Design guidelines.
In other words, we ...

- Simplify component usage
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

components (with a s)

@jfcere jfcere merged commit b5e2b92 into master Nov 2, 2017
@jfcere jfcere deleted the scote-update-readme branch November 2, 2017 17:10
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants