I’ve been working on custom place types over at https://github.com/yunity/karrot-backend/pull/1122 - I left it a while, but now on revisiting it, I’m thinking I can simplify what I did already, but maybe needs a bit of thought again about what custom place types are actually for.
My open question is actually about place statuses more than types. Currently places can have one of these statuses:
- just created
- co-operating (active)
- don’t want to co-operate (declined)
And of those, only co-operating (active) can have activities. This is designed for the model of organising co-operations with stores. But this is too narrow now for all the use-cases of places.
Firstly, the custom place types could be things like:
- distribution centre
- meeting place
- public fridge
(each could have a icon, so you can see them on the map, and also filter them by type).
But then the question comes back to the statuses, many of those don’t really make sense for all of those place types (you don’t “co-operate” with a public fridge), but I’m getting a bit stuck thinking what to do without making it too complicated.
A few options:
- leave the statuses as they are, at least for now, just add the place types on top of it
- allow to add custom statuses, that can be used for any place type + enable activities for all non-archived statuses
- … something else?
And another part of this is whether to create a bunch of default place types, like the ones above… or leave the groups to create whatever makes sense to them.