433 patch sensor

[GustaafL]

Description

Adds an API endpoint to PATCH a sensor

Look & Feel

endpoint sensors/<id>

json:
{
"name": "POWER",
}

response:
{
"name": "POWER",
"event_resolution": "PT1H",
"unit": "kWh",
"generic_asset_id": 1,
}

Related Items

Relates to issue #433

Mention if this PR closes an Issue or Project.

---

• I agree to contribute to the project under Apache 2 License.
• To the best of my knowledge, the proposed patch is not based on code under GPL or other license that is incompatible with FlexMeasures

[nhoening]

Looks really good!

I have one concern about formalizing what attributes are excluded in the PartialSchema and how. If we get that straight (by changes or discussion), this can be merged.

[nhoening]

Thanks!

I think this is already fine, with one caveat:

As a frontend dev, I might want to get the sensor ID back from fetch_one and patch (in order to build valid API URLs for the sensor for the next action on it). I don't think that's highly critical, so it could also go into a follow-up ticket.

The GenericAssetSchema has this line, maybe adding this to the SensroSchema would accomplish this:

id = ma.auto_field()

If that works superwell, we could include it here, otherwise make a follow-up issue.

[GustaafL]

The GenericAssetSchema has this line, maybe adding this to the SensroSchema would accomplish this:

id = ma.auto_field()

If that works superwell, we could include it here, otherwise make a follow-up issue.

I've added id = ma.auto_field(dump_only) and a test that it can not be edited.

[nhoening]

Is the ID now returned in fetch_one and /or patch?

[GustaafL]

All responses that return the sensor include the id. So will also need to fix the docstrings.