polyphemus - highlight when a commit param is false #1397
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.
It can be very confusing to run a polyphemus loader, and see a log that looks like it would capture some change you know would come, but then to not see your expected update in Timur.
This can happen due to running the loader with the 'commit' param set to false. This does get injected into the log, but the one-liner is easy enough to miss.
PR adds an icon and text highlighting that the loader is set to "Dry Run Mode", with tooltip explaining further and calling out 'commit'. (Tooltip: "Parsed updates will not be 'commit'ed to the database")
