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
Hello,
First of all thanks for the awesome tool! Would you consider adding a super aggressive mode ?
I understand the potential problems about %d in #59. The workaround works fine, but in my codebase %d (or %i) is not used to convert the value, but just because the value to be stringified is an int. So in my case I have no need to add calls to int() and I'd like to simply have f"{my_int}" instead of f"{int(my_int)".
This behavior could be added as a super aggressive mode -aa, or -ti for --transform-ints.
The text was updated successfully, but these errors were encountered:
Hello,
First of all thanks for the awesome tool! Would you consider adding a super aggressive mode ?
I understand the potential problems about
%d
in #59. The workaround works fine, but in my codebase%d
(or%i
) is not used to convert the value, but just because the value to be stringified is an int. So in my case I have no need to add calls toint()
and I'd like to simply havef"{my_int}"
instead off"{int(my_int)"
.This behavior could be added as a super aggressive mode
-aa
, or-ti
for--transform-ints
.The text was updated successfully, but these errors were encountered: