This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1k
Add satisfiability check for case variants #1079
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
e64c82e
Add satisfiability check for case variants
sdboyer 5c96c10
Use case folding to normalize lookup map key
sdboyer 65c8f22
Fixes off-by-one error; rename method
sdboyer 538f5d3
Add a bunch more test cases
sdboyer 8670e66
Add wrongCaseFailure
sdboyer 6592101
Case insensitivity magic for roots in fixtures
sdboyer 3d369c5
Add the wrongCaseFailure, and scads more fixtures
sdboyer 56ce3a4
Add test for import path case-sense handling in SM
sdboyer 70d2f5b
Tests for combined source & case variance
sdboyer bddd3f4
Treat ProjectRoot as case-insensitive in srcCoord
sdboyer a665a6e
Accommodate case folding in older mgr test
sdboyer 9e038e6
Ensure URLs are folded as well
sdboyer 101c2d9
gps: Add helpful debugging info to test logging
sdboyer cbf0318
gps: don't fold inputs to root deduction
sdboyer File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
NBD, but for cases like this, sometimes I like to define a struct for the test state, with a
run
method:Then instead of:
You get:
Which reads nicely, and avoids the multi-level closure and indentation hell that sometimes comes with these sorts of tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mm yes, good point, i am being lazy with these. table-based declaration of them is more generally standard and does look better. i keep seeing your changes come in and thinking "i should remember to declare like that 😛 "