-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Labels
featureMajor new functionality requiring significant implementationMajor new functionality requiring significant implementation
Description
Summary
Support for including files that aren't compiled models - static assets, resources, or passthrough files.
Open Questions
- Naming:
[[static]],[[resources]], or something else? - Location: Should they go in
models/dir, or a separatestatic/orresources/dir? - Ref-ability: Can they be
ref()'d by models?- If yes: do we track them for staleness? If a static file changes, do consumers recompile?
- If no: they're just copied to output for downstream consumers
- Manifest tracking: Do they appear in the manifest? Who "owns" their metadata?
- Subgraph behavior: When running
colin compile specific.md, are static files included? (Probably yes - "always copy to output")
Context
Mentioned in #22 as [[static]] config in colin.toml, but deferred from initial {% file %} implementation.
Use cases:
- Including a logo or image in output
- Bundling a schema file that models reference
- Copying config templates that don't need compilation
Related
- Implement multi-file output #22 - Multi-file output ({% file %} directive)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
featureMajor new functionality requiring significant implementationMajor new functionality requiring significant implementation