Option to hide/remove the injected line with the "scan" and "try it" action links

[Osndok]

I don't recall when these appeared, but I find these two links to be quite bothersome. Relatedly, neither one is functional, so I don't get any utility from their presence either. There presence greatly disrupts the document which is otherwise a homogenous field of inert, selectable, and mutable text.

Alternatively, perhaps they should be hidden by default unless 42Crunch credentials are present?

For context, as one who primarily values this plugin simply to "linkify" the yaml references, I am currently debating whether the added nuisance of these floaty widgets in the text file outweighs the value-add of the reference-linking feature. My hope is that it is just going through an awkward phase of life.

[vfateev]

If we are talking about scan links you are right, it should be hidden by default, unfortunately there was an internal technical reason not to do it. But of course in future releases we will add the possibility to hide them if a user doesn't have the credentials. Right now they can be turned off in Settings / Editor / Inlay Hints / Other / JSON or YAML / Conformance Scan.
As for try it links, they don't depend on the credentials and it is quite useful for our customers that is why it is enabled by default. We will add the possibility to hide them as well. Thank you for your opinion.

[karelhusa]

@vfateev, I have turned off the Conformance Scan Inlay hints, but the hints still appear in the editor.

No change happened, even after restarting PyCharm. Both Scan and Try it marks are present in the editor.

[vfateev]

No need to restart, just press the apply & ok buttons, if it doesn't work like that, then it is a PyCharm issue.

[karelhusa]

@vfateev With apply & ok buttons, no change.

It's hard to distinguish if the issue resides in the plugin or PyCharm itself. Also, if I report the issue to JetBrains, they do not support 3rd party plugins.

If you have any advice on how to solve such issues, please let me know.

[ak1394]

It looks like this is something for us to look at. We'll re-test with PyCharm, and if the issue persists we'll open an issue at IntelliJ bug tracker, for them to fix it.