Replace {@includeCode} with synced code fences
#328
Merged
+1,776
−96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrate JSDoc and markdown documentation from
{@includeCode ./file#region}tags to inline code fences with{source="./file#region"}attributes. Code examples are now visible directly in source files while remaining type-checked via their.examples.tssource files.Add
scripts/sync-snippets.tsto extract code from//#regionblocks and sync it into labeled fences. Run withnpm run sync:snippets.@ochafik This is based on what we talked about in #302 (comment). Getting TypeDoc to omit custom (inline) tags would likely require a TypeDoc plugin, so I ended up using code fence attribute syntax instead, which I think works nicely.