DXCDT-304: Logs output display absolute time #590
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔧 Changes
As reported by #418 , the date output in
auth0 logs tailis not useful because it displays in relative time (ex: "5 minutes ago"). This is a problem because the logs stream output does not update the rows that have already rendered, meaning that the time displayed is stuck to a moment in the past. Instead, the logs tail output should display absolute time so that the time displayed is never incorrect. Unfortunately, this same logs output is used for theauth0 logs showcommand, which would not have the same problem as the above. However, it is currently not possible to separate the rendering logic for each command.📚 References
Original issue: #418
📝 Checklist