-
Notifications
You must be signed in to change notification settings - Fork 379
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
[Composer] Allow imagine-library version 0.7.0 #958
Merged
Merged
Changes from all commits
Commits
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
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.
The
,<0.8
is not necessary.^0.7.0
means>=0.7.0 <0.8.0.
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 realize; I believe the current syntax was used to provide clarity, as even before the change when it was
^0.6.3,<0.7
, the<0.7
was unnecessary. It's important to note that the rule you mentioned only applies for fully enumerated versions [above1.x
], so it may be a good idea to retain the upper constraint so when someone comes along and changes it to, say^1.0
, we don't open the floodgates.There are a bunch of ways to write this, such as
^0.6.3|^0.7.0,<0.8
,>=0.6.3,~0.6,<0.8
,>=0.6.3,<0.8
or~0.6.3|~0.7.0
(the latter of which I personally prefer), but the original intention seems to have been verbosity, which the current syntax provides, no?If anything, I'd prefer
~0.6.3|~0.7.0
, honestly.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.
^0.7
and^0.7.0
are actually equivalent. But I understand your point. It is more clear for those who don't know how the the caret operator works.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 meant to append that with "above
1.x
" and I obviously used the wrong example of0.7
where I intended to use1.0
. Was typing quickly. ;-)