Conversation
Single-file structure is idiomatic for small CLI tools that aren't intended as libraries. At ~320 lines, the code is easily scannable in one file without jumping between files. This also improves consistency with mdembed, another pinned repo with similar single-purpose CLI tool characteristics. Ordering: imports → const/types → main() → functions by receiver. Co-authored-by: Warp <agent@warp.dev>
Mirrors the source file consolidation for consistency. At ~270 lines, the tests are easily scannable in one file. TestMain stays at the top as test infrastructure, followed by unit tests, then the integration test. Co-authored-by: Warp <agent@warp.dev>
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
1 participant
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.
Single-file structure is idiomatic for small CLI tools that aren't
intended as libraries. At ~320 lines, the code is easily scannable
in one file without jumping between files.
This also improves consistency with mdembed, another pinned repo
with similar single-purpose CLI tool characteristics.
Ordering: imports → const/types → main() → functions by receiver.
Also consolidate test files. This mirrors the source file
consolidation for consistency. At ~270 lines, the tests are
easily scannable in one file.
TestMain stays at the top as test infrastructure, followed by unit
tests, then the integration test.
Co-authored-by: Warp agent@warp.dev