csharp
public interface IImportExecutorWhatever actually runs an importer.
No guide page documents this yet — the page shows what the code says about itself.
Remarks
The seam Tools/Vixen.AssetCompiler plugs into. Everything else about an import — which importer claims the file, what the cache key is, whether anything needs to run at all, what gets written back to the sidecar — stays in ImportPipeline where there is one copy of it. What crosses the boundary is one asset's worth of work.
Methods (1)
ValueTask<ExecutedImport> ExecuteAsync(ImportJob job, CancellationToken cancellationToken = default(CancellationToken))Runs one import.
Used by (6)
- CompilerPoolVixen.AssetCompiler
- CompilerPoolTestsVixen.AssetCompiler.Tests
- ContentPipelineVixen.Editor.Assets
- ImportPipelineVixen.Editor.Assets
- InProcessImportExecutorVixen.Editor.Assets
- WorkerHostVixen.AssetCompiler