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
The current API routes are a bit messy and likely to change along with future improvements. It would be very messy if 3rd party software becomes reliant on the current API elements.
How should we deal with this?
Documentation should declare particular API elements as guaranteed to be unchanging in future versions of Baron?
Should the API be versioned within the route path?
Should stable API elements be within a marked object within views to differentiate from not stable?
The text was updated successfully, but these errors were encountered:
The current API routes are a bit messy and likely to change along with future improvements. It would be very messy if 3rd party software becomes reliant on the current API elements.
How should we deal with this?
The text was updated successfully, but these errors were encountered: