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 Feb 26, 2020. It is now read-only.
I am working on creating a POST version of the current GET api endpoints. And organizing the routes to a routers folder, converting the current controller scripts to modules. It will also leave the GET endpoints still usable as is.
This way we can introduce optional parameters, e.g. message or custom fees etc.
Thoughts on this?
The text was updated successfully, but these errors were encountered:
Go for it.
Please mind that new routes should be covered with acceptance tests (the way they are covered now).
Also, if those changes arent backward compatible - increase the major version number (ver 3+)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am working on creating a POST version of the current GET api endpoints. And organizing the routes to a routers folder, converting the current controller scripts to modules. It will also leave the GET endpoints still usable as is.
This way we can introduce optional parameters, e.g. message or custom fees etc.
Thoughts on this?
The text was updated successfully, but these errors were encountered: