-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update driveitem-list-children.md #9470
base: main
Are you sure you want to change the base?
Conversation
Added clarification when using additional filter parameters on children.
Learn Build status updates of commit 51024a4: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
@@ -174,6 +174,11 @@ Content-type: application/json | |||
"@odata.nextLink": "https://..." | |||
} | |||
``` | |||
> [!IMPORTANT] | |||
> Children requests that contain additional $filter parameters are not supported. For example: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 43 of this article lists the supported query parameters and it doesn't include $filter
. If the filter parameter isn't supported for this API, do we need this note? Otherwise, do we need to update the Optional query parameters section to reflect that $filter
is supported?
Hello @Spucelik! This pull request has been inactive for 2 weeks with the
Note Pull requests that are inactive more than 6 weeks will be automatically closed. |
Hello @Spucelik! This pull request has been inactive for 4 weeks with the
Note Pull requests that are inactive more than 6 weeks will be automatically closed. |
Added clarification when using additional filter parameters on children.
Important
Required for API changes:
Add other supporting information, such as a description of the PR changes:
ADD INFORMATION HERE
Important
The following guidance is for Microsoft employees only. Community contributors can ignore this message; our content team will manage the status.
After you've created your PR, expand this section for tips and additional instructions.
#feedback-addressed
to the pull request.For more information, see the Content review process summary.