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
Description
Right now our home page is render a static list of events. This was done so that the assets and presentation of events could be completed without having to be concerned with where the data was coming from.
This ticket is to retrieve event data from the bager-me-api repo for our app - the host name where it's being currently hosted is contained therein. The endpoint itself should be GET /activities
Ideally the endpoints themselves should be configurable within the project so that our code doesn't reference static endpoints and instead rely on internal configuration (perhaps using Preferences) to know where to route our requests.
It's worth remembering also that the endpoint require authorisation so we may need to revisit how we persist user authentication data when they login so that we can make these requests.
As this is a technical task there aren't any acceptance criteria as such, just get the data from the server. For now we're going to make the (unrealistic) assumption that the server will always return a 200-like response in a timely manner and handle unhappy path cases another time.
The text was updated successfully, but these errors were encountered:
Description
Right now our home page is render a static list of events. This was done so that the assets and presentation of events could be completed without having to be concerned with where the data was coming from.
This ticket is to retrieve event data from the bager-me-api repo for our app - the host name where it's being currently hosted is contained therein. The endpoint itself should be
GET /activities
Ideally the endpoints themselves should be configurable within the project so that our code doesn't reference static endpoints and instead rely on internal configuration (perhaps using Preferences) to know where to route our requests.
It's worth remembering also that the endpoint require authorisation so we may need to revisit how we persist user authentication data when they login so that we can make these requests.
As this is a technical task there aren't any acceptance criteria as such, just get the data from the server. For now we're going to make the (unrealistic) assumption that the server will always return a 200-like response in a timely manner and handle unhappy path cases another time.
The text was updated successfully, but these errors were encountered: