-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Would Love More Directory Structure Examples #103
Comments
I disagree with the proposal of placing user interface elements within the
Considering the existing example project content structure, I propose a new subfolder within the Example
I have not thought about potential subfolders. |
On second though, maybe the following structure would make sense:
|
The current directory structure guidelines are on the right track, but painfully vague. I'd love a lot more examples in that section. For example, we aren't sure where best to put UI-related stuff in the folder structure prescribed. We're thinking likely
Core/UI
.As another example, where should input actions go? We don't want to put them in a folder called
Core/InputActions/
because section 2.6 indicates that you should not create folders specific to the type of an asset. I consideredCore/Input/
so that all input-related content can go there (e.g., binding contexts, etc.) but I'd also expect that the input actions and binding contexts that go with a particular UI context would go with that context. So, perhaps,Core/UI/<Name of Screen>
would be better?The text was updated successfully, but these errors were encountered: