Closed jfaigan closed 1 year ago
@jfaigan Thanks for the report! I assume this still worked with 5.6.0?
No problem. Yes, I have both 5.6 and 5.7 running in parallel on different ports.
Here is what 5.6 yields:
This has been fixed with b3a80d1b767f90a7790ac378d7e88107d1ad5482 for 5.8, which we can hopefully finalize real soon now.
Affected version
Name the affected version, i.e. "release x.y.z" or "revision".
5.7.0
...
Steps to reproduce
How can the incorrect behaviour be reproduced?
Expected behaviour
What would be the correct/expected behaviour?
Type element should be provided as per the API documentation
Actual behaviour
What behaviour can actually be observed instead of the correct behaviour?
Type element is not in the returned json
Additional information
Other data that can help with fixing the defect, e.g. logs, screenshots etc.