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
What is the problem you are trying to solve with this feature?
Currently, lot of features already exists for Items but are missing for Locations. There are several issues opened to also implement them for locations (qr code, pictures, maintenance...)
What is the solution you are proposing?
In order to simplify code base, merging items and locations into a single entity will enabled to share all features between items and locations.
The original idea is taken from hay-kot/homebox#696.
To sum up, the idea is to use only one table for everything and add a type column (item or location for now) + a parent column.
I haven't looked yet into details, but it should solve all those issues :
We're already looking into doing this, we have a roadmap we're working on putting finishing touches on and we'll release that to the community most likely immediately after the next version is released.
What is the problem you are trying to solve with this feature?
Currently, lot of features already exists for Items but are missing for Locations. There are several issues opened to also implement them for locations (qr code, pictures, maintenance...)
What is the solution you are proposing?
In order to simplify code base, merging items and locations into a single entity will enabled to share all features between items and locations.
The original idea is taken from hay-kot/homebox#696.
To sum up, the idea is to use only one table for everything and add a
type
column (item
orlocation
for now) + aparent
column.I haven't looked yet into details, but it should solve all those issues :
What alternatives have you considered?
No response
Additional context
No response
Contributions
The text was updated successfully, but these errors were encountered: