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
Currently, the endpoint /api/v1/equipment-types/ return a list of all equipment types as well as their associated items (see below). This is useful for an admin who wishes to see a list of all items, but doesn't provide functionality for a member to view what items are available during a certain timeframe.
Current behavior with GET /api/v1/equipment-types/:
Create a new API GET endpoint that, given the timeframe as query strings, return the same list of all equipment types but with the status of each item.
Desired behavior with GET /api/v1/equipment-types/?out=<time>&in=<time>/, where <time> is a string of the format %Y-%m-%dT%H:%M:%S%z:
Use the API endpoint /api/v1/availability/ as a reference, which also takes in query strings ?out=<time>&in=<time>, except it also takes an ID and returns the availability of only one equipment item.
In order to add the "available" field, it probably isn't a good idea to add a new field to the EquipmentItem model, since this is a field that is dependent on dynamic information.
The text was updated successfully, but these errors were encountered:
Currently, the endpoint /api/v1/equipment-types/ return a list of all equipment types as well as their associated items (see below). This is useful for an admin who wishes to see a list of all items, but doesn't provide functionality for a member to view what items are available during a certain timeframe.
Current behavior with GET /api/v1/equipment-types/:
Create a new API GET endpoint that, given the timeframe as query strings, return the same list of all equipment types but with the status of each item.
Desired behavior with GET /api/v1/equipment-types/?out=<time>&in=<time>/, where <time> is a string of the format %Y-%m-%dT%H:%M:%S%z:
Use the API endpoint /api/v1/availability/ as a reference, which also takes in query strings ?out=<time>&in=<time>, except it also takes an ID and returns the availability of only one equipment item.
In order to add the "available" field, it probably isn't a good idea to add a new field to the EquipmentItem model, since this is a field that is dependent on dynamic information.
The text was updated successfully, but these errors were encountered: