public static class BuiltInImportersThe importers this build of the engine has.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
One list, in one place, and told rather than discovered. An assembly scan for [Importer] would read metadata a trimmed publish has already deleted; worse, it would make "which importers imported this project" a question with a different answer in the editor, in the CLI and in a worker process.
That last one is why this moved out of the CLI. A worker whose registry differs from its coordinator's produces different artefacts for the same file, and the disagreement shows up as a cache that never hits — or, worse, as a build whose output depends on how many cores the machine has.
Methods (2)
public static ImporterRegistry Create()Builds the registry.
public static ImporterRegistry Create(ImporterContributions contributed)Builds the registry over a particular set of contributions.
Used by (6)
- AssetEditorRegistryTestsVixen.Editor.AssetEditors.Tests
- CompilerPoolTestsVixen.AssetCompiler.Tests
- CreateMenuTestsVixen.Editor.App.Tests
- ImporterContributionTestsVixen.Editor.Assets.Tests
- ProjectWorkspaceVixen.Editor.Assets
- WorkerHostVixen.AssetCompiler