Replies: 4 comments 3 replies
-
Hello @mart-e, could you please try adding the |
Beta Was this translation helpful? Give feedback.
-
Hi, The |
Beta Was this translation helpful? Give feedback.
-
We don't have any current plans to enhance the logging, but since it sounds reasonable, I don't want to close it. |
Beta Was this translation helpful? Give feedback.
-
@codegaze Hi, Thanos. I just upgraded to the Go version of the Transifex client after the old client stopped working very recently; it fails by printing hundreds of HTML and JS lines to the screen (I understand that the API endpoint had to be closed, but it's still kind of funky to see the older program do that instead of maybe showing a proper JSON error explaining where to go) and I agree with the original request. My problem with the standard level of output is also that, seemingly due to how the buffering works, it's constantly clearing and recreating all lines, causing a dizzying level of flickering on Windows, and making the scrollbar not very useful. If you want to easily test this, pull this repository and run this script on Windows, no dependencies required: https://github.com/tldmod/tldmod/blob/master/Languages/tx.cmd The other thing is that I don't find half of the lines very interesting, the lines tend to show very redundant information. |
Beta Was this translation helpful? Give feedback.
-
Hi,
When doing a
tx pull
, the new script is very verbose and does not allow to easily filter debug, info, warning and error messages.while the log in the previous version of the CLI looked like:
where it was easy to filter out info and warning messages.
Fetching the translations of our project, was 15k lines of INFO but only a few were actual WARNING and ERRORs.
With the new CLI, fetching the same project migrated, it is now 31k lines where it's hard to spot the warning or errors.
Beta Was this translation helpful? Give feedback.
All reactions