Skip to content
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

Fix scan_finished JSON MessageType #4176

Merged
merged 2 commits into from Mar 12, 2023
Merged

Conversation

LXGaming
Copy link
Contributor

@LXGaming LXGaming commented Jan 27, 2023

What does this PR change? What problem does it solve?

This PR corrects the MessageType of the verboseUpdate struct which is printed by the ReportTotal function, the MessageType is currently set to status instead of verbose_status, This causes the message to be misidentified as a statusUpdate when deserializing JSON.

Was the change previously discussed in an issue or on the forum?

Not that I'm aware of.

Checklist

  • I have read the contribution guidelines.
  • I have enabled maintainer edits.
  • I have added tests for all code changes.
  • I have added documentation for relevant changes (in the manual).
  • There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
  • I have run gofmt on the code in all commits.
  • All commit messages are formatted in the same style as the other commits in the repo.
  • I'm done! This pull request is ready for review.

Corrected the scan_finished JSON MessageType from status to verbose_status
Copy link
Member

@MichaelEischer MichaelEischer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

I've slightly tweaked the changelog file and rebased the PR>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants