fix: Avoid unnecessary field resets in the API Request component #7544
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes some issues related to field reset in the API Request components:
use_curl
property is active before proceeding with the field reset.else
clause from_update_method_fields
to avoid unnecessarily resetting fields toadvanced
.else
clause from_update_curl_mode
to only set a field asadvanced
whenuse_curl
is set.Test Evidence 1
Before ⬇️
After ⬇️
Test Evidence 2
Before ⬇️
After ⬇️