Fix incorrect generation of commands with aliases #279
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
gabdube
pushed a commit
to gabdube/ash
that referenced
this pull request
Mar 23, 2020
* Fix incorrect generation of commands with aliases * Use alias name instead of the actual cmd name
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.
Ash still uses vkxml in some parts which is not aware of command aliases, and therefore we had a few extensions that were just empty.
So instead of upgrading ash to vk_parse everywhere, this PR just uses the alias information of vk_parse as a workaround.
This should fix 3 open PRs
#278
#276
#262