-
Notifications
You must be signed in to change notification settings - Fork 2
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
v2.0.0: compatibility with PhyloNetworks v0.17; output named tuple (breaking, #21 fix) #26
Merged
Changes from 18 commits
Commits
Show all changes
19 commits
Select commit
Hold shift + click to select a range
5651cdc
depend on PhyloTraits, for 2-trait substitution models
cecileane 625efeb
removed substitutionmodels.jl and PhyloTraits dependency
cecileane 9bc0cd2
deprecated readTopology -> readnewick
cecileane 5dc7688
internal names of edge/node/net fields
cecileane dd8d5ed
removed deprecated old method
cecileane 6109ffd
fixed arg types previously hidden by defaults
cecileane 07a5919
CamelCase to smallcase: directedges, tiplabels, majortree
cecileane 0e983fe
Camel to small: resetnodenumbers
cecileane 8e00556
doc make: checkout master branch of PN
cecileane d208a4b
tagbot permissions
cecileane 35dfa2d
fixed and added links to examples, readme
cecileane 9ae3922
fix #21: return named tuple
cecileane ec056dd
install qpdf on macos manually before setup-r
cecileane b4f835a
key names in docstring
cecileane 0eeceb1
Remove space before ':' for style consistency
pbastide 5142d90
Remove manual qpdf install. setup-r issue should be fixed by v2.11.1
pbastide f655988
Fix typos and punctuation for consistency
pbastide 09b6f9a
rightwards phylogram to use terminology of ape::plot.phylo
pbastide e7c0bde
v2.0.0 due to breaking change. righwards without phylogram
cecileane 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 was deleted.
Oops, something went wrong.
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
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.
I'm fine with 1.1.0, but out of curiosity, what made you change your mind and not go to 2.0.0 ?
(As it is a non backward compatible change, see #20 (comment))
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, indeed, it should be 2.0.0. When starting this PR, I merely wanted a version compatible with the new PhyloNetworks v0.17.0. Later I noticed the open issue #21 and thought that it was a good time to act on it, introducing a breaking change.
I also agree with removing "phylogram", but it would be nice to keep the term "rightwards" to be explicit that these plots won't convey the "semidirected" nature of networks like "circular" trees can do.
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.
Thank you, looks good to me !