Vixen
02b45cc4
csharp
public static class ContentPipeline

Importing and building a project, as calls that return data rather than print it.

No guide page documents this yet — the page shows what the code says about itself.

Remarks

The orchestration the CLI had, with the console taken out of it. Each step is a component that already existed; what lives here is the order they go in and the part that has to touch a filesystem. It reports through a callback rather than to a writer, because an editor puts a diagnostic in a panel and a tool puts it on stdout, and neither should own the other's output format.

⚠ A build packs what the import produced, so the two are ordered and not alternatives. The plan reads the import cache; a build run against a project that has never been imported plans nothing and writes an empty catalog, which looks exactly like a build that worked. Callers that mean "make me a build" call both.

Fields and properties (3)

  • public const string HashFileSuffix

    What the build writes beside the catalog, so a static host needs nothing else.

  • public const string CatalogFileName

    The catalog's file name, which is what a runtime and a server both expect.

  • public const string SceneManifestFileName

    What the scenes-in-build manifest is called, beside the catalog.

Methods (4)

Used by (9)

  • ContentBuildRunnerVixen.Cli
  • ContentPipelineTestsVixen.Editor.Assets.Tests
  • ContentTasksVixen.Editor.App
  • EditorApplicationVixen.Editor.App
  • EditorContentTestsVixen.Editor.App.Tests
  • ImportRunnerVixen.Cli
  • LooseContentVixen.Editor.Assets
  • LooseContentTestsVixen.Editor.Assets.Tests
  • SceneManifestTestsVixen.Editor.Assets.Tests