New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use diff engine #644
Merged
Merged
Use diff engine #644
Changes from 2 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
3e69bfb
use diffengine
SimonCropp b167006
.
SimonCropp 5e7ecdc
add obsoletes
SimonCropp 1748da8
Update Shouldly.csproj
SimonCropp 3682642
Merge branch 'master' into useDiffEngine
SimonCropp a6f0d88
Merge branch 'master' into useDiffEngine
SimonCropp 0b4856c
Merge branch 'master' into useDiffEngine
SimonCropp c0510c5
Update ApprovePublicApi.ShouldlyApi.approved.cs
SimonCropp 96b3fe0
Update ShouldMatchApprovedScenarios.cs
SimonCropp File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
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 was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
23 changes: 0 additions & 23 deletions
23
src/Shouldly/Configuration/DoNotLaunchWhenEnvVariableIsPresent.cs
This file was deleted.
Oops, something went wrong.
10 changes: 0 additions & 10 deletions
10
src/Shouldly/Configuration/DoNotLaunchWhenPlatformIsNotWindows.cs
This file was deleted.
Oops, something went wrong.
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.
How will existing code using Shouldly v3 know what to do upon upgrading to v4?
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.
Is it possible in principle to preserve Shouldly's existing API and delegate to DiffEngine for the implementation?
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.
I added obsoletes
i would prefer not to. reasons:
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.
I have toyed with the idea of avoiding a nuget ref. submodules or a source package. but ultimately the docs was too difficult to replicate
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.
thoughts on the above? this PR changes enough that i am holding of on the next few things
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.
That answers my question, thanks. I was thinking it could ease the transition, but if we want the obsoleted APIs to continue working in v4, we should just leave the v3 impl intact. If we don't, I think I'm good with that with the caveat that I haven't used diffing so I don't have a good sense of what people might expect.