Add intellisense for macros defined by \NewDocumentCommand #4126
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 PR closes #3995 and adds (partial) intellisense support for macros defined by
\ReNewDocumentCommand,\NewDocumentCommand,\ProvideDocumentCommand,\DeclareDocumentCommandfrom thexparsepackage.These commands expect three arguments:
{macro_name},{args_list),{definition}. The argument list allows to define argument that have their own delimiters such as(...),<...>, or the same token used for opening and closing as in the\verbcommand. This is not supported for now as ourCmdSignatureinterface only handles compulsory arguments{}or optional ones[]. The current implementation only supports the following types in the argument listm: a mandatory argumentoorO: an optional argumentAnything else is simply ignored.