You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an issue with the patch_feature_flag_with_http_info method in the LaunchDarkly API Client library. Even when the Content-Type header is provided, it gets overwritten, which causes the semantic patch requests to fail.
Steps to Reproduce
Call the patch_feature_flag_with_http_info method to make a semantic patch request.
Set the Content-Type header to application/json; domain-model=launchdarkly.semanticpatch.
Observe that the Content-Type header does not retain the provided value and is instead set to application/json.
Expected Behavior
The Content-Type header should retain the provided value and include domain-model=launchdarkly.semanticpatch to comply with the LD API Docs for semantic patch requests.
Actual Behavior
The Content-Type header is overwritten to application/json, causing the request to fail.
Additional Information
I have created a pull request with proposed changes to address this issue. Please take a look: (#5)
Thank you!
The text was updated successfully, but these errors were encountered:
Description
There is an issue with the
patch_feature_flag_with_http_info
method in the LaunchDarkly API Client library. Even when theContent-Type
header is provided, it gets overwritten, which causes the semantic patch requests to fail.Steps to Reproduce
patch_feature_flag_with_http_info
method to make a semantic patch request.Content-Type
header toapplication/json; domain-model=launchdarkly.semanticpatch
.Content-Type
header does not retain the provided value and is instead set toapplication/json
.Expected Behavior
The
Content-Type
header should retain the provided value and includedomain-model=launchdarkly.semanticpatch
to comply with the LD API Docs for semantic patch requests.Actual Behavior
The
Content-Type
header is overwritten toapplication/json
, causing the request to fail.Additional Information
I have created a pull request with proposed changes to address this issue. Please take a look: (#5)
Thank you!
The text was updated successfully, but these errors were encountered: