What happened?
Bug Report
While the plugin is active, some options under Settings > Editor > Color Scheme > Python become useless, meaning that while they still allow to modify the default option, such changes have no effect.
These are the ones i found, but i suspect there might be other examples.
| n |
... |
...overridden by |
| 1 |
Python/Function Definition |
Python/Function Call (or Language Default/Function Call) |
| 2 |
Python/Nested Function Definition |
Python/Function Call (or Language Default/Function Call) |
| 3 |
Python/Special Names/Definition |
Python/Function Call (or Language Default/Function Call) |
| 4 |
Python/Special Names/Usage |
Python/Function Call (or Language Default/Function Call) |
| 5 |
Python/Built-in Name |
(depending on the token) |
Note 1: all these "overridings" only ovverride the color and not additional options (like italics or bold checkboxes)
Note 2: in the Jetbrains Quick Documentation hovering window, the one that opens upon hovering on a token or by using the Quick Documentation shortkey, the real and correct setted color value are visible, meaning the bug only seems to manifest in the editor.
Comments / Request
I understand why this bug happens, especially in the case of Built-in Name, as it would be too complicated to categorize and parametrize all the different Built-In token types (types, functions, ect). So I do not necessarily recognize that particular instance as a bug.
However, in the Function Definition (and similars) the case is different, as the plugin is basically denying the possibility to set a custom color for such options.
Expected Behaviour
Upon modifying color settings [1], [2]: their color should become the custom color selected by the user for the particular settings, and not inherted from some other setting forcefully and without notice.
Doing the same for options [3], [4] (and maybe [5] in the future) would be also great
Thanks
I am not very used to write big reports, forgive me for any mistake.
Thaks for your time.
Relevant log output or stack trace
Steps to reproduce
- [Plugin Installed]
- Create a new color theme based on a theme from the plugin OR just use one of the themes from the plugin (after the first change, the IDE will create a user-modified-copy of the theme)
- Verify that plugin is working correctly (for example look if the type annotation of a
str variable is colored as a VSCode Class/Type; without the plugin active, Pycharm defaults to a Purple-ish color)
- Modify any of the options I specified in the table (for example Python/
Function Definition)
- Check the effects: you will notice the change did not work (it only works in the case specified in Note 2). Instead the color will still be the color you would see on a default VSCode theme (in this case the color a VSCode Function, which does not make distinction between FunDefinition and FunCall in the default settings).
Gradle IntelliJ Plugin version
1.12.0
Gradle version
???
Operating System
Windows
Link to build, i.e. failing GitHub Action job
No response
What happened?
Bug Report
While the plugin is active, some options under
Settings > Editor > Color Scheme > Pythonbecome useless, meaning that while they still allow to modify the default option, such changes have no effect.These are the ones i found, but i suspect there might be other examples.
Function DefinitionFunction Call(or Language Default/Function Call)Nested Function DefinitionFunction Call(or Language Default/Function Call)DefinitionFunction Call(or Language Default/Function Call)UsageFunction Call(or Language Default/Function Call)Built-in NameNote 1: all these "overridings" only ovverride the color and not additional options (like
italicsorboldcheckboxes)Note 2: in the Jetbrains Quick Documentation hovering window, the one that opens upon hovering on a token or by using the Quick Documentation shortkey, the real and correct setted color value are visible, meaning the bug only seems to manifest in the editor.
Comments / Request
I understand why this bug happens, especially in the case of
Built-in Name, as it would be too complicated to categorize and parametrize all the different Built-In token types (types, functions, ect). So I do not necessarily recognize that particular instance as a bug.However, in the
Function Definition(and similars) the case is different, as the plugin is basically denying the possibility to set a custom color for such options.Expected Behaviour
Upon modifying color settings [1], [2]: their color should become the custom color selected by the user for the particular settings, and not inherted from some other setting forcefully and without notice.
Doing the same for options [3], [4] (and maybe [5] in the future) would be also great
Thanks
I am not very used to write big reports, forgive me for any mistake.
Thaks for your time.
Relevant log output or stack trace
Steps to reproduce
strvariable is colored as a VSCode Class/Type; without the plugin active, Pycharm defaults to a Purple-ish color)Function Definition)Gradle IntelliJ Plugin version
1.12.0
Gradle version
???
Operating System
Windows
Link to build, i.e. failing GitHub Action job
No response