Corrected logical flaw in "split..." terminology. #1833
Closed
Conversation
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
Also added terse variants to refer to split axes.
Collaborator
|
Feed back from the community session. We have discussed this and came to the conclusion that we prefer today's action names. Also if we want to rename actions we need to deprecate the old names and still keep those around so we don't break people's setup. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Also added terse variants to refer to split axes: "split why" for "split vertical", and "split ex" for "split horizontal".
splits.talondescribes the reasoning behind this. This is similar to stacking layouts from UI frameworks (React, Slint) where the stacking direction is opposite to the direction of the split lines between the cells.