EXOAntiPhishPolicy: Change var PhishThresholdLevel type #4687
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.
Pull Request (PR) description
Variable PhishThresholdLevel is of type string, but in reality it's actually an integer (valid from 1 to 4), in fact the exports already are generated that way and include integers and not strings.
This is affecting my unit tests since I'm generating my own blueprints which take the type of the variable from the schema which is string but the resulting blueprint comes up with an integer and therefore they fail.
Usually this would be considered a breaking change but in this case it doesn't affect the current exports because they already follow the reality and PhishThresholdLevel is exported as an integer, see below.
This Pull Request (PR) fixes the following issues