microsoftgraph / microsoftgraph/msgraph-metadata
Flagged enums referenced as collections.
Open
Nobody has claimed this yet.
priority:p2
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
Description
- Type
windows10XSCEPCertificateProfilereferencesgraph.hashAlgorithmsas a collection whengraph.hashAlgorithmsis already a Flagged enum. Other references/documentation involve a single value enum. https://learn.microsoft.com/en-us/graph/api/intune-rapolicy-windows10xscepcertificateprofile-create?view=graph-rest-beta graph.authenticationMethodModesis always referenced as a collection of in the metadata despite it being a flagged enum type. Other references/documentation point it to be being serialized a single value in a collection. appliesToCombinations property at https://learn.microsoft.com/en-us/graph/api/authenticationcombinationconfiguration-get?view=graph-rest-beta&tabs=httpconditionalAccessConditions is no longer referenced as a collection
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the metadata definitions and references for windows10XSCEPCertificateProfile, graph.hashAlgorithms, graph.authenticationMethodModes, and appliesToCombinations, then compare them with the linked Microsoft Graph documentation. Done means the flagged enum references are represented consistently as single values rather than collections, while the withdrawn conditionalAccessConditions point remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100