Replies: 4 comments
-
|
I had considered the possibility of expanding # %i represents taskID
# %p represents "pad", so appearing at the end would be "right pad"
turbo run --log-prefix='format:%i%p
# %p at the beginning would be left-pad
turbo run --log-prefix='format:%p%iWhat do you think of that? I'm not sure how/if we'd allow |
Beta Was this translation helpful? Give feedback.
-
|
That would be cool! Alternatively... and this could be a stretch, but still want to suggest it – you could support what @roarr/cli does and allow a configuration file with log formatting rules. I'd prefer this because it would allow to perform other useful features, like filtering, throttling, resolving paths in logs, etc. in user-land. |
Beta Was this translation helpful? Give feedback.
-
|
Structured logging all around is a great idea. We are currently planning for an upcoming release to take a look at logging holistically. We can take a look at this if/when that sprint happens. |
Beta Was this translation helpful? Give feedback.
-
|
Structured logging is great, but in this case, I simply meant a config file that defines a callback that gets unstructured log message that I can post-process myself. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Which project is this feature idea for?
Turborepo
Describe the feature you'd like to request
Pad logs to the length of the longest workspace+task name.
Consider these logs:
If
contra-temporal:devis the longest name in the repo, then with the proposed option, these logs would be adjusted to:It just makes reading logs easier.
Describe the solution you'd like
N/A
Describe alternatives you've considered
N/A
Beta Was this translation helpful? Give feedback.
All reactions