What problem does this solve or what need does it fill?
I have a game where many of the different types of assets will all be YAML files, but with different schema and corresponding Rust structures. For example, I may have a dude1.character.yml and a weapon2.weapon.yml file.
What solution would you like?
It would be nice if Bevy asset loaders could be configured to match on the multi-dot file extension. So that I could register a custom asset loader that will load all character.yml files, instead of having to do character-yml files, just to differentiate the different type of YAMLs in my project.
What alternative(s) have you considered?
I can work around it for now just by adding syntax highlighting associations for the character-yml file format, but it's not ideal.
Additional context
The biggest motivation is to keep the system and my IDE treating the .character.yml files as actual YAML and not getting confused when it sees a .character-yml file.
What problem does this solve or what need does it fill?
I have a game where many of the different types of assets will all be YAML files, but with different schema and corresponding Rust structures. For example, I may have a
dude1.character.ymland aweapon2.weapon.ymlfile.What solution would you like?
It would be nice if Bevy asset loaders could be configured to match on the multi-dot file extension. So that I could register a custom asset loader that will load all
character.ymlfiles, instead of having to docharacter-ymlfiles, just to differentiate the different type of YAMLs in my project.What alternative(s) have you considered?
I can work around it for now just by adding syntax highlighting associations for the
character-ymlfile format, but it's not ideal.Additional context
The biggest motivation is to keep the system and my IDE treating the
.character.ymlfiles as actual YAML and not getting confused when it sees a.character-ymlfile.