Repository navigation
Conversation
disallow `,` in DEPS_COMMENT improve parsing of DEPS_ANNOT assume there is no more `)` after the annotation fixes kscripting#166
Contributor
Author
|
it has become obvious to me this attempt is fighting windmills, i will open a new PR |
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
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.
specifying
[1.0)as version was broken, because kscript would not pass the correct values to the POMdisallow
,in DEPS_COMMENT;and space should still workimprove parsing of DEPS_ANNOT
use
.substringBeforeLast(")")instead of.split(")")[0]assume there is no more
)after the annotationmaybe also make sure
//.+is stripped before?is there no smarter annotation parser available ?
fixes #166