Filter clause not working anymore in ItemsRequestBuilderGetQueryParameters
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by running the reported reproduction against SDK version 1.15.0, using ItemsRequestBuilder.ItemsRequestBuilderGetQueryParameters and RequestConfiguration. Compare the result with the suggested ChildrenRequestBuilder workaround and verify whether the filter is sent and applied. Done means the request returns only the folder named "some_name".
Written by the indexing model from the issue text.
Description
Describe the bug
I have a query that's using this code to retrieve a folder by name:
onedrive = await client.me.drive.get()
query_params = ItemsRequestBuilder.ItemsRequestBuilderGetQueryParameters(
filter="name eq 'some_name'"
)
config = RequestConfiguration(query_parameters=query_params)
subfolder = (await client.drives.by_drive_id(onedrive.id).items.get(request_configuration=config)).value
but suddenly it's not working anymore.
The filter based on the name just returns all 200 subfolders of onedrive.
Expected behavior
Just the folder with "some_name" is retrieved
How to reproduce
onedrive = await client.me.drive.get()
query_params = ItemsRequestBuilder.ItemsRequestBuilderGetQueryParameters(
filter="name eq 'some_name'"
)
config = RequestConfiguration(query_parameters=query_params)
subfolder = (await client.drives.by_drive_id(onedrive.id).items.get(request_configuration=config)).value
SDK Version
1.15.0
Latest version known to work for scenario above?
No response
Known Workarounds
Maybe switching to ChildrenRequestBuilder and using items.by_drive_items_id(ID).children.get(query_params with name filter)
Debug output
Click to expand log
```</details>
### Configuration
_No response_
### Other information
_No response_
- Dominant language
- Python
- Stars
- 630
- Forks
- 96
- Avg merge
- 15h 20m
- Merged PRs (30d)
- 3
Contributor guide
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-sdk-python
-
status:waiting-for-triage type:bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
microsoftgraph/msgraph-sdk-python#1570 ·
-
status:waiting-for-triage type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoftgraph/msgraph-sdk-python#1563 ·
-
Needs: Attention :wave: type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoftgraph/msgraph-sdk-python#1287 · 2 comments · 1 reaction ·
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 52/100
microsoftgraph/msgraph-sdk-python#1578 ·
-
status:waiting-for-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoftgraph/msgraph-sdk-python#1557 ·
All issues in microsoftgraph/msgraph-sdk-python
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
canonical/paas-charm#368 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
tech debt
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
StevenBlack/hosts#3256 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
qualcomm/qai-appbuilder#275 ·