SpaceApi
Replace `beverage_supply` with a more generic `products` field
Right now there is no way of displaying the availability of snacks and components. Deprecating beverage_supply and replacing it with products with a new type field to discern the product type could resolve that.
I'm not opposed to implementing this. I also don't think there's many changes needed in the schema - mainly renaming the sensor from beverage_supply to products and adding additional units. I don't even think the type property is needed; the unit, name and description of the sensor should be sufficient.
@Freddo3000 what units would you like to see in this new products sensor?
Right now I can think of:
- btl (bottles; already in
beverage_supply) - crt (crates; already in
beverage_supply) - pcs (pieces; new)
@SpaceApi/core any thoughts from your side?
Are you sure you meant no. 20? That one contains every unit from A·m² (Ampere-squaremeter) to parsec.
@SpaceApi/core any thoughts from your side?
I agree, this probably makes sense. However, is "products" the proper name? It's maybe a bit too generic. If I sell Arduino kits, would I list them as well?
Are you sure you meant no. 20? That one contains every unit from A·m² (Ampere-squaremeter) to parsec.
Yes. But on a more serious note it should probably be a string field instead of an enum as there's simply too many units. Cans, bottles, kits, pcs, catridges, bundles, etc. I'm not sure if there's any other suitable standard to refer to other than UNECE Rec 20/21, and it should probably not be opinionated.