Add arrows #21
Merged
Add arrows #21
Conversation
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
TODOs: update documentation, update argument so it allows for arrow distance changes, color specs, size, etc.
Tests, roxygen documentation added
1 note from xend in add_arrows
rsh52
added
documentation
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.
Background
This PR introduces arrows as an additional visualization element to
ggswim(), updates the documentation, and adds a supporting article.At present, arrows are tucked into
ggswim()via a few arrow arguments, but could be broken out into anadd_arrows()separate function.Pros of current setup:
Cons of current setup:
geom_segment()and technically add a new layer. This makesggswim()a two layer function instead of a single layer function