-
Notifications
You must be signed in to change notification settings - Fork 39
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
Open PRs for compat entries to weak dependencies #458
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
3e26709
Track deps also in weakdeps
sethaxen 1a37f99
Add dependency section to PR title
sethaxen fc254ae
Fix keyword bug
sethaxen 45974be
Add section to other method
sethaxen cabbdae
Update new_versions tests
sethaxen 313d2be
Update method call
sethaxen 499cc6d
Update patch
sethaxen dcc3043
Run formatter
sethaxen 6c640c2
Add integration tests for weak dependencies
sethaxen fcb78b0
Place square brackets around section name in title
sethaxen 3978cb2
Add unit test for `get_project_deps`
sethaxen 3e52390
Don't change the PR title when package is in deps section
sethaxen 4bde1bf
Merge remote-tracking branch 'upstream/master' into weakdeps
sethaxen 8c7b462
Increase count for pr length check
sethaxen a8420c1
Merge remote-tracking branch 'upstream/master' into weakdeps
sethaxen 59d661e
Merge branch 'master' into weakdeps
sethaxen 5b8461c
Add missing compat entries for extras
sethaxen 5e1aedf
Increment minor version for feature release
sethaxen c3ea3bf
Merge branch 'master' into weakdeps
sethaxen 0cffa34
Update call to `get_project_deps`
sethaxen 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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
name = "compathelper_integration_test_repo" | ||
uuid = "0e97b93d-f6aa-40c8-b749-d2f6bf239ed7" | ||
authors = ["Brown Center for Biomedical Informatics"] | ||
description = "Test Project.toml with both dependencies and weak dependencies, compat entries; major ver, ~" | ||
version = "0.1.0" | ||
|
||
[weakdeps] | ||
BioSequences = "7e6ae17a-c86d-528c-b3b9-7f778a29fe59" | ||
DataFrames = "a93c6f00-e57d-5684-b7b6-d8193f3e46c0" | ||
Flux = "587475ba-b771-5e3f-ad9e-33799f191a9c" | ||
IterableTables = "1c8ee90f-4401-5389-894e-7a04a3dc0f4d" | ||
Nettle_jll = "4c82536e-c426-54e4-b420-14f461c4ed8b" | ||
PGFPlotsX = "8314cec4-20b6-5062-9cdb-752b83310925" | ||
Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40" | ||
|
||
[extensions] | ||
Ext = ["BioSequences", "DataFrames", "Flux", "IterableTables", "Nettle_jll", "PGFPlotsX"] | ||
|
||
[compat] | ||
IterableTables = "1" | ||
PGFPlotsX = "~1.0.0" | ||
julia = "1.2" | ||
|
||
[extras] | ||
Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40" | ||
|
||
[targets] | ||
test = ["Test"] |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
name = "compathelper_integration_test_repo" | ||
uuid = "0e97b93d-f6aa-40c8-b749-d2f6bf239ed7" | ||
authors = ["Brown Center for Biomedical Informatics"] | ||
description = "Test Project.toml with weak dependency where package does not exist" | ||
version = "0.1.0" | ||
|
||
[weakdeps] | ||
ThisPackageDoesNotExist = "2c58d03c-75de-479c-aa0b-96bf0b358d76" | ||
|
||
[extensions] | ||
Ext = "ThisPackageDoesNotExist" | ||
|
||
[compat] | ||
julia = "1.2" | ||
|
||
[extras] | ||
Test = "8dfed614-e22c-5e08-85e1-65c5234f0b40" | ||
|
||
[targets] | ||
test = ["Test"] |
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.
what if a package is in multiple sections? E.g.
[deps]
and[weakdeps]
is a documented compatibility strategyThere 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.
Ah, I had thought it would make sense to always note that is in
[deps]
vs[weakdeps]
(or in the future[extras]
), but yes, the case covered in that docs page is one where one would want to highlight[weakdeps]
. Perhaps then it makes sense to list no section in the PR title when the dependency is only in[deps]
and otherwise give a comma-separated list of sections (currently[weakdeps]
or[deps], [weakdeps]
)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.
If it’s only the title it seems like not too big of a deal either way, just wanted to make sure semantically it was OK. Maybe a simple choice is to just use deps in the title when present by looping over weak deps then deps (or vice versa if you prefer)
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.
Ah, that's currently how this works.
get!(dep_section, compat_entry, section)
ensures thatdep_section[compat_entry]
is only set once to a section for a given package, and if the package was found in thedeps
section, it's already set, soweakdeps
will be ignored.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.
If possible, I'd like the titles for regular deps to remain the same as the old titles, and for the new title format to only be used for weakdeps.
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.
@DilumAluthge this has already been handled in 3e52390