-
Notifications
You must be signed in to change notification settings - Fork 114
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
feat: add support for form format #4000
Conversation
Allure Test reports for this run are available at: |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #4000 +/- ##
===========================================
+ Coverage 90.78% 90.81% +0.03%
===========================================
Files 624 626 +2
Lines 32553 32677 +124
Branches 7727 7757 +30
===========================================
+ Hits 29552 29676 +124
Misses 2777 2777
Partials 224 224 ☔ View full report in Codecov by Sentry. |
e85a96a
to
15afa4f
Compare
Allure Test reports for this run are available at: |
Allure Test reports for this run are available at: |
Allure Test reports for this run are available at: |
Allure Test reports for this run are available at: |
f74972e
Allure Test reports for this run are available at: |
Allure Test reports for this run are available at: |
Allure Test reports for this run are available at: |
|
What are the changes introduced in this PR?
form-urlencoded
format. Send payload inbody.FORM
if format isFORM
excludeMappedFields
xmlns:xsi
namespaceWhat is the related Linear task?
Resolves INT-2983
Please explain the objectives of your changes below
Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here
Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?
N/A
Any new dependencies introduced with this change?
N/A
Any new generic utility introduced or modified. Please explain the changes.
N/A
Any technical or performance related pointers to consider with the change?
N/A
@coderabbitai review
Developer checklist
My code follows the style guidelines of this project
No breaking changes are being introduced.
All related docs linked with the PR?
All changes manually tested?
Any documentation changes needed with this change?
Is the PR limited to 10 file changes?
Is the PR limited to one linear task?
Are relevant unit and component test-cases added in new readability format?
Reviewer checklist
Is the type of change in the PR title appropriate as per the changes?
Verified that there are no credentials or confidential data exposed with the changes.