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
After installing duster with no custom config whatsoever - the command ./vendor/bin/duster lint successfully highlights errors regarding global_namespace_import rule (under Linting using TLint section), but running ./vendor/bin/duster fix does not actually fix these imports.
this is marked with Fully Qualified Class Names should only be used for accessing class names warning, but the ./vendor/bin/duster fix command doesnt fix it. it just goes LGTM!
The text was updated successfully, but these errors were encountered:
TLint doesn't fix this linting issue. I looked into it but couldn't find a way to do it reliably. There are too many edge cases having to do with name collisions.
I'll leave this open for now as I consider a solution related to #124 where, if TLint discovers a listing issue, the fix command still fails.
After installing duster with no custom config whatsoever - the command
./vendor/bin/duster lint
successfully highlights errors regardingglobal_namespace_import
rule (under Linting using TLint section), but running./vendor/bin/duster fix
does not actually fix these imports.Example:
this is marked with Fully Qualified Class Names should only be used for accessing class names warning, but the
./vendor/bin/duster fix
command doesnt fix it. it just goesLGTM!
The text was updated successfully, but these errors were encountered: