bugfix/email-toAllAuthorized - use proper variable to set toAllAuthorized for Email class #255
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.
Description
While leveraging the gem, identified a bug in the Email class where the assignment for toAllAuthorized uses an uninitialized variable instead of the properly defined @to_all_authorized varaible.
Motivation and Context
Currently it is not possible to create or update a report which has the setting enabled to send to all authorized users. With this change, this functionality will begin to work as intended.
How Has This Been Tested?
Limited testing against a local Nexpose 6.4.7 environment. Tested the creation of new reports with setting enabled, along with the updating of current reports.
Types of changes
Checklist: