Add multiselect support for sequence command #50
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
|
Published to marketplace. |
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.
First off, thanks for making this extension. It's super helpful.
This change improves the multiselect support for the sequence command by making it more consistent with IntelliJ's String Manipulation plugin. I see the issue was already reported in #47.
This change adds a new
multiselectDataobject that is passed to all number functions (although onlysequenceuses it currently) to allow data to be stored between calls. In this case,sequenceuses it to keep track of the current number (offset) across selections. This allows the user to create a sequence of numbers in a column without affecting other numbers on each row. For example:Becomes...
Let me know if you have any questions or feedback, thanks.