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
Hi, great tool, but I have a bit of a UX nitpick. By default, every time you run bump-pydantic it generates log.txt in the current directory. This is usually at the project root of a repo and I really don't care about the log file 99% of the time, and I have to remember not to accidentally git commit it. I would add a rule but for a basically one-off process it seems unnecessary.
I think it would be a better experience if it did one of the following:
Don't generate a log file unless --log-file option is requested
Generate a log file in an inconsequential dir by default (e.g. /tmp/bump-pydantic/log.txt)
Accept --no-log-file to suppress the generation of the log file. (I suppose I can --log-file=/dev/null but I have to remember that each time)
The text was updated successfully, but these errors were encountered:
Hi, great tool, but I have a bit of a UX nitpick. By default, every time you run
bump-pydantic
it generateslog.txt
in the current directory. This is usually at the project root of a repo and I really don't care about the log file 99% of the time, and I have to remember not to accidentally git commit it. I would add a rule but for a basically one-off process it seems unnecessary.I think it would be a better experience if it did one of the following:
--log-file
option is requested/tmp/bump-pydantic/log.txt
)--no-log-file
to suppress the generation of the log file. (I suppose I can--log-file=/dev/null
but I have to remember that each time)The text was updated successfully, but these errors were encountered: