@separate, @unite, @summary #18
Merged
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
drizk1
changed the title
|
@drizk1 is this ready to merge from your standpoint? |
|
I can take a look at the docstring issue for |
|
That would be awesome. I can't figure out how to reproduce the evaluated output because it omits the last column due to width so the expected won't match evaluated. |
added 2 commits
August 4, 2023 08:13
|
We'll figure out the docstrings later - I updated this PR with the changes from the main branch and will merge this PR for now. In a future update, we can considering making |
|
Incredible. I'll def start moving @summary towards that goal |
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.
Update includes
@separate,@uniteand@summarywith docstring and examples@summarydocstring - had to use ; because table was too wide and i couldnt correctly copy width