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
As of a42244f, the analyzer now generates context messages in some circumstances explaining why type promotion failed. IntelliJ integration exposes these messages to the user via a right click on the error message. We would like these messages to show up in a way that's more easily discoverable.
Yesterday we discussed some possibilities for how to do this. In an ideal world we'd like the "problems" view to have a tree structure so that the user can see context messages as collapsible leaves underneath the error messages. Unfortunately there are performance limitations getting in the way of doing this when the error count is large. Possible ways around the performance issues include:
Switching to a table view when the error count is large
Automatically filtering to just the current file (or perhaps folder) when the error count is large
displaying the context messages as a new, third column in the problems view
In addition, we might want to display the context messages in the tooltips for the analysis errors.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
(Parent issue #44897)
As of a42244f, the analyzer now generates context messages in some circumstances explaining why type promotion failed. IntelliJ integration exposes these messages to the user via a right click on the error message. We would like these messages to show up in a way that's more easily discoverable.
Yesterday we discussed some possibilities for how to do this. In an ideal world we'd like the "problems" view to have a tree structure so that the user can see context messages as collapsible leaves underneath the error messages. Unfortunately there are performance limitations getting in the way of doing this when the error count is large. Possible ways around the performance issues include:
In addition, we might want to display the context messages in the tooltips for the analysis errors.
The text was updated successfully, but these errors were encountered: