extra $ sign on ListSites "search" query param
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start at the generated ListSites request builder and its RequestInformation query-parameter template. Compare the emitted query key with the API's expected search key and inspect any existing request tests or URL assertions. Done when SDK configuration produces search=%2A without the extra $, without manual RawQuery editing.
Written by the indexing model from the issue text.
Description
when setting the query params of listSites request using RequestInformation class, the template used for preparing the URL uses "$search" while the API expects "search" without the "$" sign.
To work around it I had to patch the httpRequest manually:
"httpRequest.URL.RawQuery = "search=%2A"
However, currently it is not supported using the SDK.
Thanks
- Dominant language
- Go
- Stars
- 332
- Forks
- 43
- Avg merge
- 6h 42m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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-go
-
ItemItemsItemPermanentDeleteRequestBuilderInternal.Post missing content body/content-type headersOpenstatus:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 48/100
microsoftgraph/msgraph-sdk-go#980 ·
Maintainers usually reply within 1 day
-
status:waiting-for-triage type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoftgraph/msgraph-sdk-go#972 ·
Maintainers usually reply within 1 day
-
status:waiting-for-triage type:bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoftgraph/msgraph-sdk-go#969 · 1 comment ·
Maintainers usually reply within 1 day
-
status:waiting-for-triage type:feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoftgraph/msgraph-sdk-go#964 ·
Maintainers usually reply within 1 day
-
status:waiting-for-triage type:feature
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoftgraph/msgraph-sdk-go#940 · 1 comment ·
Maintainers usually reply within 1 day
All issues in microsoftgraph/msgraph-sdk-go
Similar issues
-
triage/pending-triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
external-secrets/external-secrets#7117 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ENTERPILOT/GoModel#1183 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Edwin-metcalf/MetCode#16 ·
-
Action Required: Fix Renovate ConfigurationPossibly taken @thompson-tomo claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 78/100
open-telemetry/opentelemetry-collector#16170 ·
Maintainers usually reply within 1 day
-
Buffer.writeRTX drops the RTCP returned by calc, so NACKs for other lost packets are never sentOpen
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day