dylan-lang / lsp-dylan

Language Server for Dylan (alpha)
MIT License
7 stars 2 forks source link

Options to abbreviate type names #19

Open cgay opened 1 year ago

cgay commented 1 year ago

Rather than this: Class <subcommand>(<command>:command-line-parser:command-line-parser)

I would prefer this: Class <subcommand>(<command>)

In fact, I'm not sure what the current rules are. For example why does it not display Class <subcommand>:command-line-parser:command-line-parser(<command>:command-line-parser:command-line-parser)? I didn't import <subcommand> and <command> into the current module differently.

What I'm sure of is that frequently the :module:library part just makes it harder to read long parameter lists. As long as textDocument/declaration (i.e. M-.) works I can find the module and library if I need to.

cgay commented 2 months ago

At a minimum, we could remove :dylan:dylan from names exported from the dylan:dylan module. <boolean>:dylan:dylan becomes just <boolean>.

Also, perhaps some standardized abbreviation for when the module name and library name are the same. For example, :command-line-parser:command-line-parser could be :command-line-parser. That is, if there is no library part then it's the same as the module part.

These could be additional command-line options that are configurable in the client.