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 zone location type should act differently from the other location types. As it is an aggregator of locations it should not change the existing tree structure of inserted locations. Instead it sounds plausible the possibility for it to be attached to the a parent location.
Add this description to API documentation.
The text was updated successfully, but these errors were encountered:
This service requires an ad hoc structure. We need to figure out which is the best way to make it.
The best solution would be to reuse actual structure, but probably we need a new one. Probably we can add a new service called zones.
Think if we really need this before building it as it could be replaced by collections
The
zone
location type should act differently from the other location types. As it is an aggregator of locations it should not change the existing tree structure of inserted locations. Instead it sounds plausible the possibility for it to be attached to the a parent location.Add this description to API documentation.
The text was updated successfully, but these errors were encountered: