Heads-up: Resource lookup path change (under discussion) #785
Replies: 1 comment 3 replies
-
|
I like more the approach of flattening the layout, because the From my point of view, inside a scene bundle / folder everything you have is an asset, even if in the future we add some code or scripting code I call that an asset. The only thing that maybe is not an asset could be some configuration files, outside the scene description file, but for now I think we can place these config files in the root folder. |
Beta Was this translation helpful? Give feedback.
-
|
So, we should remove the parent "Asset" folder? I think that is a cleaner approach. I'll update my branch and let you know when it's up. Also, I'm writing new docs with all these changes. The new website should be up by Friday. |
Beta Was this translation helpful? Give feedback.
-
|
Changes have been merged. |
Beta Was this translation helpful? Give feedback.
-
|
I will merge this tonight to update my branch and resolve any possible conflict |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
TL;DR
I’m making a small behavior change so the Main bundle follows the same directory structure as a custom base path. The Module bundle remains the same. This is open for discussion before we lock it in.
What’s changing:
assetBasePath (existing layout) and Bundle.main will both search using the same relative subpaths:
Bundle.module behavior is effectively unchanged.
Why
Unifies lookup rules so developers use one predictable folder layout regardless of whether assets come from a base path or the main app bundle.
Impact
Open question
Should we drop the top-level Assets folder and use a flatter scheme?
I’ll adjust the shared search list (and docs) based on team preference.
Beta Was this translation helpful? Give feedback.
All reactions