Skip to content

Add missing MEL log levels to the LogLevel validation (#2235) #2236

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

eitamal
Copy link

@eitamal eitamal commented Jun 21, 2025

Summary

This PR adds Trace, Debug, Information, Critical, and None to the validation set on the LogLevel parameter when starting PSES using Start-EditorServices.ps1 to allow for the adoption of the newer MEL log levels (#2200), closing #2235.

Context

The ValidationSet defined for LogLevel 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).

…ervices.ps1 (PowerShell#2235)

This commit adds `Trace`, `Debug`, `Information`, `Critical`, and `None`
to the validation set on the `LogLevel` parameter when starting PSES
using `Start-EditorServices.ps1` to allow for the adoption of the newer
MEL log levels.
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.

1 participant