Does anybody else feel this way about @spec (visually overpowering)?

I don’t really agree, but why not just change your theme to make up for it? It’s not very likely to change based on the idea of it being too visually distinctive.

but why not just change your theme to make up for it

That’s not necessarily a simple thing to do. That’s why I’m asking around.

What editor and theme are you using? I don’t know of any modern editor/IDE that doesn’t have (comparatively) easy theme management.

I think he means, changing the spec thing without changing everything else.

Yeah, I’ve used a few editors and themes and none of them seem to do what I want. I want to see if I’m not alone. (currently using vscode)

I think @spec should look closer in appearance to documentation than code.

In that case I suppose it’d be an issue of having the @spec part be parsed as documentation in, for example, the ElixirLS extension in VS Code. I’m not entirely sure which part does the actual parsing of the text, but presumably it’s in a public repo.

Edit:

https://github.com/JakeBecker/vscode-elixir-ls/blob/master/syntaxes/elixir.json#L25

There you can see the syntax highlighting part for docs. Adding @spec as a pattern there should probably make it so that it’s highlighted as documentation. Fork the repo, make the change, run your own version of the extension.

If it’s not exactly there, it’ll likely be as easy somewhere else in that file.

I don’t agree it’s visually overpowering.

@spec is a part of code not a part of documentation. It defines really important thing, types for function parameters and type of function return value, which helps in code readibility and code understanding.

Side note:

In PHP types should be written in function clause:

public function getIntegrationProvider(int $provider_id): IntegrationProvider
{
}

This is pretty secondary to his own taste. If he wants to run an extension that treats it visually as documentation, that’s really his prerogative. I think the bigger point here is that it’s probably better to look to your tooling rather than try to make changes on a compiler/community level.

Yep. You are rigth.

And keep up with bug fixes, patches and releases. Which is why I said it’s not necessarily a simple thing to do.

I’m not trying to change the language or compiler. I’m trying to see if there are other people who feel the same way I do and if they have found or come up with any good solutions.