Add property-based URL builder tests#81
Open
RomanOstr wants to merge 1 commit into
Open
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
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.
Summary
Why
These request-building paths are sensitive to optional filters, paging defaults, and encoding. Property-based tests cover a much wider input space than a few hand-written examples and help prevent regressions in query construction.
Scope
This PR is limited to URL-building refactors and property-based test coverage. It does not include fork-only publishing, policy, or release changes.
Validation
npm run lintnpm run test:propertynpm run buildNote: local
npm run format:checkon this Windows worktree reported broad pre-existing formatting drift across tracked TypeScript/JSON files, so GitHub Actions on Linux should remain the source of truth for formatting on this PR.