Expose House (and others) over API

mcab commented 5 years ago

Seems like this requires a lot of knowledge about serialization.

mcab commented 5 years ago

In order for this to work, we probably will need another Serializer for HouseInformation.

This can be used as an optional parameter passed with the House one, or standalone on a different path (house/information?)

Something of the sorts. For now, we have it at least Authenticated, and need to have a Permission that is AuthenticatedAndOwnerOrAdmin or something like that.

mcab commented 5 years ago

HouseEnvironmentFeatures got a ViewSet, but the problem is routing properly for it.

We need to be able to:

GET the most recent environment features for that house (nested in House ViewSet)
GET a LIST of all the environment features for that house (list view on HouseEnvironmentFeatureViewSet, probably GET /api/v1/house/{pk}/environment)
POST to /api/v1/house/{pk}/environment to create a HouseEnvironmentFeatures, tied to that PK.
PUT/PATCH? to /api/v1/house/{house pk}/environment/{environment pk} with some revision add-on so that we can view / edit certain traits.

Maybe we don't even need to implement DELETE. Ideally, we keep the records, so that we can map changes to the environment / physical bathouse.

We want to probably do this by nesting ViewSets [1] [2]. This then extends to physical features, and we can then start mocking out what Flightplan expects.

mcab / hiber

Expose House (and others) over API #29