check session status...
Bug Fix Report
Generate a Fixed Bugs Report for a single version, or for all bugs fixed between any two versions (inclusive).
| Found 4 bugs fixed in 11.1.0 |
| Bug ID | Component | Platform | Status |
| When an invalid @Sort directive is used (such as missing the direction property), an internal error message is returned instead of a valid GraphQL response | |||
| When an invalid @Sort directive is used (such as missing the direction property), then an internal error message is returned instead of a valid GraphQL response that includes the error in the "errors" property. | |||
| BUG-60070 | all | Fixed in 11.1.0 | |
| The @sort directive is unrecognized unless it is capitalized as @Sort. | |||
| The directives should be normalized to all be lower-case. However, @Sort was missed. | |||
| BUG-60069 | all | Fixed in 11.1.0 | |
| An empty "errors" array is included in the JSON when there are no errors | |||
| When there are no errors, the response JSON includes an "errors" property with an empty array as the value. This is a violation of the GraphQL specification. | |||
| BUG-60064 | all | Fixed in 11.1.0 | |
| When an invalid date is used for one of the range filters, an internal error message is returned instead of a valid GraphQL response | |||
| When an invalid date is used for one of the range filters (such as @greaterThan), then an internal error message is returned instead of a valid GraphQL response that includes the error in the "errors" property. | |||
| BUG-60068 | all | Fixed in 11.1.0 | |