You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The event is sent by the server after it registers all of the LSP handlers. However both of these will happen well before you connect. When you connect to DTD, we transmit all registered services so you know they're available, but because initialized is an event, there's no re-transmission of that.
I don't know if it makes sense to re-transmit events like this, because this event was quite LSP-specific. Ignoring initialized, a client generally wouldn't want to know that DTD has finished sending it the existing services, because in general there's nothing to say new services won't be registered milliseconds later.
I wonder if the simplest thing would be for the property editor to just show a spinner until it has the services it expects registered, perhaps with a timeout (of a few seconds) that says no editor is available? In theory, no users should see this because the editors shouldn't be showing a property editor iframe when those services would not be available?
See comment here: #8598 (comment)
The text was updated successfully, but these errors were encountered: