Rafał Chłodnicki

I'm talking about [codeActionProvider.codeActionKinds](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#codeActionOptions) capability which accepts an array of kinds.

The LSP spec author admitted in https://github.com/microsoft/language-server-protocol/issues/1629#issuecomment-2268446838 that if the code action is not registered in `codeActionProvider.codeActionKinds` then the editor should not utilize it for the "code actions on save"...

It works here with a manually triggered exception like this: ``` this.$sentry.withScope((scope) => { scope.setExtra('x', { 1: { 2: { 3: { 4: { 5: { 6: { 7: {...

> For the mentioned features that are rendered in the view (e.g. via phantoms) it should be handled in `DocumentSyncListener` instead to choose the `best_session` and then distributed only to...

I kinda feel like technically handling it from SessionBuffer is the correct thing to do since the result is specific to the particular session. We might want to instead try...

Nowhere in the documentation does it say that `$config.sentryDsn` or `$config.sentryEnv` are supported by the module - https://sentry.nuxtjs.org/configuration/runtime-config

Oh, you've just added those for debugging I guess. You can configure DSN and ENV with runtime config the way it's documented and it should work. The `sentry.dsn` setting (the...

No, not entire. From the docs: > Currently, only the config, clientConfig and serverConfig [options](https://sentry.nuxtjs.org/configuration/options) can be configured using the runtime config. Note that those 3 objects will be merged...

Check messages logged in the terminal. Also make sure that `process.env.OPTIMISER_WEB_SENTRY_DSN` is defined. Though I would imagine that you wouldn't want to enable Sentry during development (unless maybe for testing).

> Nothing in terminal, just same error in the console The module always logs some lines on nuxt start.