-
-
Notifications
You must be signed in to change notification settings - Fork 71
Closed
Labels
type:featureNew feature or improvement of existing featureNew feature or improvement of existing feature
Description
New Feature / Enhancement Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
Current Limitation
At the moment, if you define a struct which doesn't match your server payload, you get no meaningful errors that help you isolate the problem.
Feature / Enhancement Description
Add a .invalidStruct
error with information as to where the struct doesn't match the server payload
Example Use Case
Current response:
"Error decoding parse-server response: Optional(<NSHTTPURLResponse: 0x6000019d1100> { URL: http://localhost:1337/1/classes/GameScore } {
Better response:
"Invalid struct: No value associated with key CodingKeys(stringValue: "score", intValue: nil) ("score")."
Alternatives / Workarounds
3rd Party References
michaelnew
Metadata
Metadata
Assignees
Labels
type:featureNew feature or improvement of existing featureNew feature or improvement of existing feature