Skip to content
This repository has been archived by the owner on Mar 1, 2019. It is now read-only.

Pattern File Naming Convention #43

Open
danielmgalan opened this issue Jul 13, 2016 · 0 comments
Open

Pattern File Naming Convention #43

danielmgalan opened this issue Jul 13, 2016 · 0 comments

Comments

@danielmgalan
Copy link
Contributor

danielmgalan commented Jul 13, 2016

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.

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

No branches or pull requests

1 participant