component.md
: Component Naming Conventions better consistency
#903
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi everybody. You will find in this PR about Component Naming Conventions Guide part 4 points I propose to update:
TitleCase
There is one « Title case » term so to follow all others I change it into « TitleCase »
Case vs Cased
In first part and old second part version you used kebab-cased-component with letter « d ».
In second part you not use « d ». I think it's a better choice to kept consitency accross naming
Opened and Closed tag in exemple
I know it's possible to say « there is too verbose » but you have not already explain that is possible to use self-closed format
<my-component />
when you use following exampleSo there is two way:
Space
I have add a space in self-closed format to respect what you have done in part 3.