-
Notifications
You must be signed in to change notification settings - Fork 13
Logging improvements when plugin version mismatches with connected ES version #247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mashhurs
merged 6 commits into
elastic:main
from
mashhurs:log-improvements-when-versions-mismatch
Jan 27, 2025
Merged
Changes from 5 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
ddaa1a3
Logging improvements: informing which ES version considered when buil…
mashhurs e373d9e
Preflight check initialization optimization.
mashhurs d03f20e
Unit tests added, failed integration test cases fixed.
mashhurs b61b374
Refactored messages in a way for better visibility. Any major mismatc…
mashhurs e4dc62d
Standardize log outputs on console.
mashhurs d58fb8c
Remove forgotten heredocs style and rearrange warning texts to improv…
mashhurs File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The intent of my prior suggestion to use heredocs was to enable the text to be readable with line-breaks, but I missed an important bit where even squiggle-heredocs keep the newlines 🤦🏼.
I don't think that the squiggle-heredocs are inherently more readable though, so it might be worth going back to normal strings.
or with concatenation (each needs a trailing space)
or a heredoc, but with trickery to turn the newlines into spaces:
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was the hardest part actually!
heredocs had a power here to highlight the warnings with multiline texts. However, when I did an actual test
Overall, it looks to me our current standard loggings has a better readability (smooth reading experience) and concentration (not jump words) points.
In case of readability, yes a) I forgot to remove heredocs styles b) made unit tests readable instead actual logic (had a sleep disorder 5AM commit, sorry) - thank you for revisiting
My last commit rearranges (your 2nd suggestion, concatenation with trailing space) and removes heredocs style!
