Fix bug when populating command alias value in command metadata JSON #2788
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
Ndiritu
changed the title
Ndiritu
force-pushed
the
fix/command-metadata-alias
branch
from
d9e084d to
42b7dd3
Compare
timayabi2020
approved these changes
Jun 25, 2024
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.
Previous check would always set aliases to
nullwhen command metadata is being updated post-generation with the latest cmdlets.Setting
nullaliases causes unit tests for aliasing inFind-MgGraphCommandto fail, breaking the build pipeline.(Draft PR: pending a build pipeline run to update the command metadata.json with aliases)