You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First there seems to be a mismatch between API spec and implementation, as leaving out the collect object completely (which should be possible as it is optional) yields the following result:
To be discussed:
We propose that you should either leave out the collect object completely or - when submitting the object - use both parameters id and valid_until. So the whole collect object should be optional but the attributes of the collect objects itself should both be required.
We also changed this in the API v29 spec.
The text was updated successfully, but these errors were encountered:
JuAlMan
changed the title
Change request regarding meta.collect object
API 2.9: Change request regarding meta.collect object
Aug 5, 2024
Using image docker.sunet.se/dc4eu/apigw:apiv28
First there seems to be a mismatch between API spec and implementation, as leaving out the collect object completely (which should be possible as it is optional) yields the following result:
It only works when using an empty object.
To be discussed:
We propose that you should either leave out the collect object completely or - when submitting the object - use both parameters id and valid_until. So the whole collect object should be optional but the attributes of the collect objects itself should both be required.
We also changed this in the API v29 spec.
The text was updated successfully, but these errors were encountered: