`microsoft.graph.managedDevice` is missing a filter restrictions annotation.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- api
Research direction
Start by comparing this issue with #225 and its fix in #227, then inspect the managedDevice type description and the deviceManagement/managedDevices navigation property metadata. Done means the existing per-property filter support is represented by a FilterRestrictions annotation so generated clients no longer treat the collection as fully filterable.
Written by the indexing model from the issue text.
Description
Filtering is only partially supported on /deviceManagement/managedDevices (microsoft.graph.managedDevice), but there is no Org.OData.Capabilities.V1.FilterRestrictions annotation on the type or on the deviceManagement/managedDevices navigation property. The only place the restriction is recorded is the type description:
Devices that are managed or pre-enrolled through Intune. Limited support for $filter: Only properties whose descriptions mention support for $filter may be used, and combinations of those filtered properties must use 'and', not 'or'.
With FilterRestrictions absent, Filterable defaults to true, so the metadata advertises the collection as fully filterable. Generated clients follow the metadata: Get-MgDeviceManagementManagedDevice exposes -Filter and the .NET client exposes Filter on the request configuration, with no machine readable signal about which properties actually work. Today a caller has to read the description of each property one at a time to find out.
The per property descriptions already record which properties support $filter, so the information needed for the annotation is already in the metadata.
Same shape as #225, which was fixed by #227.
- Dominant language
- XSLT
- Stars
- 166
- Forks
- 55
- Avg merge
- 16h 12m
- Merged PRs (30d)
- 14
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.
More from microsoftgraph/msgraph-metadata
-
ToTriage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoftgraph/msgraph-metadata#1192 ·
-
ToTriage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoftgraph/msgraph-metadata#1169 · 1 reaction ·
-
ToTriage
Difficulty 3/5 1-2 days Newbie friendliness 55/100
microsoftgraph/msgraph-metadata#1166 ·
-
machine OpenToTriage
Difficulty 5/5 Over a week Newbie friendliness 15/100
microsoftgraph/msgraph-metadata#1143 ·
-
ToTriage
microsoftgraph/msgraph-metadata#1088 · 1 comment · 1 assignee ·
All issues in microsoftgraph/msgraph-metadata
Similar issues
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100