fix: split on > for sequence mappings#40
Merged
knubie merged 2 commits intoknubie:masterfrom Mar 8, 2023
Merged
Conversation
Owner
|
Awesome, thanks for the contribution @mikesmithgh ! |
Contributor
Author
|
Hey @knubie I am moving from draft to ready for review. I have been using it without any issues. |
knubie
approved these changes
Mar 8, 2023
Owner
|
Thanks @mikesmithgh ! I assume this closes #5? |
Contributor
Author
This file contains hidden or 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
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.
This is a draft PR, I had an issue mapping with
ctrl+w>lsyntax. I came up with this approach but have not checked for edge cases or side effects. I'll move out of draft after further investigation or you can pick up as well.Thanks for the kitten! 😸