Simon Sobisch

Looks like possibly the [`registerDocumentSymbolProvider` part](https://code.visualstudio.com/api/language-extensions/programmatic-language-features#show-all-symbol-definitions-within-a-document) for "common" symbols and the [`registerWorkspaceSymbolProvider`](https://code.visualstudio.com/api/language-extensions/programmatic-language-features#show-all-symbol-definitions-in-folder) for global entry points (=`procedure divisions` and `ENTRY` in outermost programs) as well as `EXTERNAL` items may be...

Wouldn't that also allow to provide a universal version (= one that works on all of Windows/Linux/Web)?

There's now a CI version called "web" - is this planned for the web (as hinted by the vsix name) or is this more a "universal" issue (as hinted by...

I think that "universal" can be understood, after all that's every extension which is not platform specific https://code.visualstudio.com/api/working-with-extensions/publishing-extension#platformspecific-extensions (and obviously there's also a "web platform"). And that's also how open-vsx...

Several changes done here (at least the parts that change hard-wired entries to variables) seem reasonable in any case. Can those get it with a direct commit/separate PR so that...

not sure of your time schedule for beta, but I'd suggest to opt for early release (= no, or context-free completion)

I don't think @lefessan had that in mind already, but that would be useful.

@lefessan What's your take on this PR?

All marketplaces, as well as other clients, render README (see #50) and CHANGELOG as well as the metadata entries from package.json. I therefore would suggest to close this as duplicate...

Even as a reminder I'd suggest to move that to the alpha release milestone.