Cargo Features
leafwing_manifest has no features set by default.
[dependencies]
leafwing_manifest = { version = "0.2.0", features = ["all_asset_loaders", "ron", "toml", "yaml", "json", "msgpack", "xml", "csv"] }
- default
-
All file formats are disabled by default: you will typically want to enable only the formats you need. Picking one per project is recommended.
- all_asset_loaders = csv, json, msgpack, ron, toml, xml, yaml
-
Support for all file format features
Useful for testing - ron all_asset_loaders?
-
Support for the RON file format
This is a good choice for most projects, as it is a simple, human-readable and plays nice with enums.Enables ron of bevy_common_assets
- toml all_asset_loaders?
-
Support for the TOML file format
This is a straightforward choice for configuration files.Enables toml of bevy_common_assets
- yaml all_asset_loaders?
-
Support for the YAML file format
This is a relatively common choice for configuration files,
and substantially more complex than TOMLEnables yaml of bevy_common_assets
- json all_asset_loaders?
-
Support for the JSON file format
JSON is nearly universal, but can be a bit verbose and nitpicky.
The key advantage is that it is well-supported by web technologies,
and has robust validation tooling.Enables json of bevy_common_assets
- msgpack all_asset_loaders?
-
Support for the MessagePack file format
This is a binary format that is more compact than JSON, but not human-readable.Enables msgpack of bevy_common_assets
- xml all_asset_loaders?
-
Support for the XML file format
XML is meaningfully more complex and less compact than JSON,
but comes with schemas and validation tools.Enables xml of bevy_common_assets
- csv all_asset_loaders?
-
Support for the CSV file format.
This is a great fit for tabular data, but notoriously flaky in edge cases due to the lack of a standard.
Good interop with spreadsheet software though!Enables csv of bevy_common_assets