-
Notifications
You must be signed in to change notification settings - Fork 705
Feature/api client post #530
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
Feature/api client post #530
Conversation
satyamsoni2211
commented
Jul 6, 2020
- Enhanced APIClient to include JSON parameters in post request
|
I have opened this pull request to directly post data as JSON instead of converting the data into JSON encoded string and passing in post API. I am using the same patch in my existing code in my organization at HSBC. |
|
Hi! |
|
Do you have plan to provide a PR with all needful changes? |
|
The purpose of using JSON parameters is to pass dict of dict as JSON directly to request body for the creation of JSD ticket. I was facing issues with post requests for multiple hierarchies of dict for custom fields containing sub child fields and options. User would now be able to use data/JSON parameters, any of them as per there convenience. |
|
I have updated PR to be backward compatible, now user can either use JSON encoded values_dict or pass it as is, the argument will be chosen based on the type of payload. |
|
@satyamsoni2211 Thank you for your update. but here that json will not transfer. based on that, could you provide your main pain about setting the json? Maybe to make wrapper for all type of requets (GET, POST , PUT etc ) |
|
I will check this out and make the required changes |
|
For future versions, I will make changes to all kinds of wrapper to accommodate the changes. Since I faced this issue with create request, I added this to the specific method, since now request method can accept JSON, I will test other methods out and can make the similar changes later on. |
|
thanks |