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
Run POST {{baseUrl}}/contact/send locally with a payload from swagger example
See that it populates with a 400.
Expected behavior
User should be created based off swagger information or update the swagger to show what it should be instead. Postman had incorrect information based off what swagger had to provide. Once the swagger is updated, can make adjustments to postman as well.
Environment
A concise description of your environment: Catalina 10.15.7. Docker version 20.10.0, build 7287ab3. NPM = 7.0.10. Ran from master branch on 12/31/2020 @ 3:00PM EST.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
The parameters provided in the body of the request sent to /contacts/send are "AND-ed" together by the backend. The seeders that populate a development database generate random values for contactIds, entityIds, and relationshipTitles. This is why the example query doesn't work with the static query provided in swagger.json. Changing the parameters to values found in the database, or an empty object, will result in a 200 Response.
The only predictable parameter for this endpoint is entityType which is hardcoded to "Test" in the seeders. So we have two choices as far as I can see. We could re-work the seeders or just fix the body of swagger.json to only include "{entityType:"Test"}"
I'd vote for the latter because there are plans to re-factor the backend entirely and effort should likely be focused there. However, I'm definitely interested in hearing what others who are more familiar with the project think.
Describe the bug
Swagger provides the following:
And it still does 400 - Bad Request.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
User should be created based off swagger information or update the swagger to show what it should be instead. Postman had incorrect information based off what swagger had to provide. Once the swagger is updated, can make adjustments to postman as well.
Environment
A concise description of your environment: Catalina 10.15.7. Docker version 20.10.0, build 7287ab3. NPM = 7.0.10. Ran from master branch on 12/31/2020 @ 3:00PM EST.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: