upgrade to libdparse 0.22.0 #713
Merged
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
PetarKirov
approved these changes
Feb 15, 2023
Member
PetarKirov
left a comment
There was a problem hiding this comment.
LGTM, though consider moving libdparse, dsymbol, DScanner and DCD into one monorepo, to streamline the development process, instead of having to do this sort of PR in the future.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
for dsymbol I lifted the strict max-version restrictions, as other projects like dscanner depend on it and often don't break. (backwards compatibility with libdparse should stay in for a while anyway)