{"version":"2.1.275","anchor":"artifact-type-descriptions-can-now-resolve-from-a-type-file","canonical_anchor":"artifact-type-descriptions-can-now-resolve-from-a-type-file","heading":"Artifact type descriptions can now resolve from a type_file reference","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/artifact-type-descriptions-can-now-resolve-from-a-type-file","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Artifact type descriptions can now resolve from a `type_file` reference\n\nArtifact type descriptions can now be resolved from a separate type_file reference instead of inline content\n\n**What**\n\nA new function handles describing an Artifact's type when that type's data lives in a separate `type_file` reference rather than being written inline. It can show either a placeholder for content that hasn't been read yet, or a preview of the actual content. The calling code also now checks a new `read_of_type_link` flag to decide whether to prefix the type's title before showing its description.\n\n**Why**\n\nThis lets Artifact type information be stored in and pulled from a separate file rather than always being embedded directly, with appropriate handling for cases where that file hasn't been read yet.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}