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
We are implementing an extension for the API where reports can have various "media", not only images. We use a mixture of (backward compatible) options:
when the calling application puts a base64 element in "media", it is processed. (uReport compatible)
When it uses a url, it is processed. (georeportv2 standard)
When it uses an array of url's these are processed. (our enhancement)
besides that, our backend does mimetype validation. (allow video, audio, images and file-urls)
Now this is a hidden extra that does not conflict with "normal" backends. But we are currently at the point where we need an extension.
For some services, like geluidsoverlast (noise disturbance) we want the calling application to know that it is not allowed to upload images, only sound. For this we want to enhance the serviceslist.
For some services, we even want the calling application to know that NO media is allowed to be posted.
Are there any implementations (in the wild) that are already using this kind of functionallity? Or are we free to design our own?
The text was updated successfully, but these errors were encountered:
We are implementing an extension for the API where reports can have various "media", not only images. We use a mixture of (backward compatible) options:
Now this is a hidden extra that does not conflict with "normal" backends. But we are currently at the point where we need an extension.
For some services, like geluidsoverlast (noise disturbance) we want the calling application to know that it is not allowed to upload images, only sound. For this we want to enhance the serviceslist.
For some services, we even want the calling application to know that NO media is allowed to be posted.
Are there any implementations (in the wild) that are already using this kind of functionallity? Or are we free to design our own?
The text was updated successfully, but these errors were encountered: