Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Add opt-in line numbers for review-oriented exports and tighten the contributor docs around
fuori's design boundaries.Changes
--line-numbersto prefix exported code lines inside fenced blocksLine numbers: onin the export header when the flag is enableddocs/design.mdinto a shorter design-boundary document focused on scope, non-goals, artifact shape, and render/selection philosophymain()consistency issue so recursive ignore-load failures go throughcleanupWhy
Line numbers are useful for code review and discussion, but they add noise for pure context-packing, so they remain opt-in. The header note makes numbered artifacts self-describing, and the design-doc rewrite keeps contributor guidance concise and durable instead of duplicating README behavior.
Verification
make testsuccessfully