-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make parameter highlighting rules more permissive #4
Comments
how do i actually get this extension functioning once installed and enabled? |
Hi, the extension should be active immediately for any Python files as soon as it is installed, no further reload or configuration required. Could you share an example of a docstring that does not get highlighted properly? |
Fixed in 36afe25. |
@jeremyvital4 Closing this issue as its original topic has been resolved - if you are still encountering issues getting the extension working, feel free to create a new issue for it. |
Many parameters end in numbers (
p1
, etc.). These are currently not picked up by the highlighting RegEx (see below).Update:
Parameters using wildcard notation (
*args
,**kwargs
) must be escaped for Sphinx to properly parse them. These escapes are currently not recognized by the highlighting rules.The text was updated successfully, but these errors were encountered: