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
Code actions get triggered on a selection and sometimes can be triggered on the whole line in terminal-based editors like vim. This might result in having multiple include-cleaner related diagnostics in the code action context. In such a scenario we'll return duplicate actions as we attach same batch-fixes to each diagnostic. e.g:
// let's say `int foo(int);` is declared in foo.h
void bar() {
[[foo(foo]](3)); // on this line we have two missing include warnings.
}
if code action gets triggered with the range between [[ ]], we'll generate multiple code actions with the same name & fix.
i believe we should de-duplicate the final code actions.
The text was updated successfully, but these errors were encountered:
Code actions get triggered on a selection and sometimes can be triggered on the whole line in terminal-based editors like vim. This might result in having multiple include-cleaner related diagnostics in the code action context. In such a scenario we'll return duplicate actions as we attach same batch-fixes to each diagnostic. e.g:
if code action gets triggered with the range between
[[ ]]
, we'll generate multiple code actions with the same name & fix.i believe we should de-duplicate the final code actions.
The text was updated successfully, but these errors were encountered: