Missing timer coverage for POST /api/pumpings

[skjdghsdjgsdj]

It looks like, while you can create a pumping entry through the web interface from a timer, the API coverage lacks the ability:

curl -v -H 'Authorization: Token ...' -H 'Content-Type: application/json'
    -X POST -d '{"child": 1, "amount": 10, "timer": 327}' 'https://.../api/pumping/'

results in:

{"id":18,"child":1,"amount":10.0,"start":"2024-05-19T16:41:49.978134-00:00",
"end":"2024-05-19T16:41:49.978145-00:00","duration":"00:00:00.000011","notes":null,"tags":[]}%

Note the duration is effectively zero, not what timer 327 was tracking.

While I could use the API to just read the start of a timer and calculate the end, then POST accordingly, it would be far simpler if the schema accepted timer IDs like feedings do, and like the web UI implies is possible.

Schema attached that shows a missing timer ID field.

[skjdghsdjgsdj]

GitHub in Firefox didn't attach the image so here's trying from Safari.

[cdubz]

Thanks for flagging. I think we just need to change the PumpingSerializer @

babybuddy/api/serializers.py

Lines 120 to 123 in 7937b23

	class PumpingSerializer(CoreModelSerializer, TaggableSerializer):
	class Meta:
	model = models.Pumping
	fields = ("id", "child", "amount", "start", "end", "duration", "notes", "tags")

to extend CoreModelWithDurationSerializer instead of CoreModelSerializer (as FeedingSerializer does).