Add missing MEL log levels to the LogLevel
validation (#2235)
#2236
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.
Summary
This PR adds
Trace
,Debug
,Information
,Critical
, andNone
to the validation set on theLogLevel
parameter when starting PSES usingStart-EditorServices.ps1
to allow for the adoption of the newer MEL log levels (#2200), closing #2235.Context
The
ValidationSet
defined forLogLevel
here: Start-EditorServices.ps1:49 was left out during the work done to enhance logging, meaning that the only MEL levels you can practically use are the ones that are the same as the legacy log levels. I chose to add the missing ones as opposed to replacing the old with the new for compatibility reasons which matched the sentiment conveyed in the code. I've included a bit more details in the issue I opened (#2235).