Describe the bug
Selecting properties in the CLI and using the JSON return type results in a JSON array of JSON objects with the unselected properties being displayed with null values. This is incorrect as those properties may have actual values in the service. We should only return the selected properties.
At some point, the CLI is taking the response and deserializing into a model. Where a property isn't returned, it automatically sets the value to null. A client that just blindly tries to parse the JSON may make the assumption that the values have been set to null.
To Reproduce
Steps to reproduce the behavior:
Run mg applications application list --select "DisplayName, Appid, SignInAudience"
Review the JSON objects returned. All of the non-selected properties are present and have the value null set.
Describe the bug Selecting properties in the CLI and using the JSON return type results in a JSON array of JSON objects with the unselected properties being displayed with null values. This is incorrect as those properties may have actual values in the service. We should only return the selected properties.
At some point, the CLI is taking the response and deserializing into a model. Where a property isn't returned, it automatically sets the value to null. A client that just blindly tries to parse the JSON may make the assumption that the values have been set to null.
To Reproduce Steps to reproduce the behavior:
mg applications application list --select "DisplayName, Appid, SignInAudience"
Expected behavior We only get back the selected properties.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
AB#9375