Inconsistent path separators for assets cause unexpected behaviours

[Joakker]

I'm working on both windows and linux, and as you know, they have different path separators. Currently BMS uses the asset's path to determine which script must be loaded where. However, if I do the following on windows

ScriptComponent::new(vec!["foo/bar.baz"])

I can't actually load the script into the entity because the asset is loaded as "foo\bar.baz". I don't want to keep track of two copies of each path changing only the separator character. I think the path should be normalised to convert \ into /

[makspll]

Hmm, so a few things to consider:

• Why not use PathBuf/Path here to avoid any issues?
• You can already do this by overriding ScriptAssetSettings, and specifically the AssetPathToScriptIdMapper, if you override there, you will be able to normalize all ScriptId's
• I am not sure asset paths always correspond to file paths, so I am a bit wary of making many assumptions here

What do you think?

[Joakker]

N°1 is how I ended up solving this issue, but I'll look into number 2. Thanks 😃

[makspll]

I should probably mention something in the docs about this, as it's a bit of a footgun!