Fix settings instance array return value #4845
Merged
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
|
Just tested it now, and yes it solves the issue but it also looks good. The thing is that you always need to battle test it, unfortunately at least as Graph API goes you need to test several times because the backend sometimes goes against you, as you've seen on your side it worked a few times and then you the same issue as I encountered. See #4771, not Graph related but this one was working for the longest time and now doesn't and it's not even about the code in M365DSC |
FabienTschanz
force-pushed
the
fix/intune-settings-catalog-settings
branch
from
aa91911 to
3e42649
Compare
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.
Pull Request (PR) description
This pull request fixes an issue where the supposed return value of an array with items was mangled to the single element by PowerShell in case there was only one element in the array.
This Pull Request (PR) fixes the following issues