You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2019. It is now read-only.
Until recently the naming convention for the repo files was Category_PatternName.ext.
But the convention is not being followed anymore.
For example, FirstRun_TrialVersion.md follows the convention previously mentioned, and Notification_Inline_Message.md doesn't. It seems that Notification files are not going to follow the convention. However, Notification_MessageBanner.md does follow it.
In a different approach, Tab_Bar.md has completely dropped the category and even further separated the name of the file into two words. It looks like navigation pattern file names only use the name of the component and will not have Navigation as a category.
Now, some file names use an underscore to separate their name if it is a compounded word. Some separate the category from the pattern name with an underscore, sometimes even if the pattern name is compounded.
If navigation file names will not include their category in their file name, I think we could change all the other files to follow this convention and simplify the entire practice of naming these files. We can still be more specific in the Readme.md file if needed.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Until recently the naming convention for the repo files was Category_PatternName.ext.
But the convention is not being followed anymore.
For example, FirstRun_TrialVersion.md follows the convention previously mentioned, and Notification_Inline_Message.md doesn't. It seems that Notification files are not going to follow the convention. However, Notification_MessageBanner.md does follow it.
In a different approach, Tab_Bar.md has completely dropped the category and even further separated the name of the file into two words. It looks like navigation pattern file names only use the name of the component and will not have Navigation as a category.
Now, some file names use an underscore to separate their name if it is a compounded word. Some separate the category from the pattern name with an underscore, sometimes even if the pattern name is compounded.
If navigation file names will not include their category in their file name, I think we could change all the other files to follow this convention and simplify the entire practice of naming these files. We can still be more specific in the Readme.md file if needed.
The text was updated successfully, but these errors were encountered: