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
{{ message }}
This repository has been archived by the owner on Jan 24, 2019. It is now read-only.
would like more info on what the motivation was for adding a status attribute to the JSON response! it adds complication to building clients on top of the API. it also strikes me as redundant as HTTP should be enough information? potentially i am missing something. thanks.
The text was updated successfully, but these errors were encountered:
Do we have a way of tracking wants for non-backwards-compatible changes in the API? We can force an update of the app, though it isn't a pretty user experience. If there are enough things that pile up, it may be worth doing at some point. -- especially while we have few users.
WARNING: Encountered "status" in payload, but no model was found for model name "status" (resolved model name using webmaker-moderator@serializer:application:.modelNameFromPayloadKey("status"))
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
would like more info on what the motivation was for adding a
status
attribute to the JSON response! it adds complication to building clients on top of the API. it also strikes me as redundant asHTTP
should be enough information? potentially i am missing something. thanks.The text was updated successfully, but these errors were encountered: