Open etanb opened 1 year ago
Potentially we could add this data to the Message Receivers object response from the backend. For reference: https://github.com/CDCgov/prime-reportstream/blob/master/prime-router/src/main/kotlin/azure/MessagesFunctions.kt#L253-L262
Potentially we could add this data to the Message Receivers object response from the backend. For reference: https://github.com/CDCgov/prime-reportstream/blob/master/prime-router/src/main/kotlin/azure/MessagesFunctions.kt#L253-L262
Is your feature request related to a problem? Please describe. Currently when we get file data from Senders, the data about the data (metadata!) is surfaced via the url. For example:
That long file name includes the file name, file type, file location and more. All split on
%2
in the URL. This not good web URL structuring for a front-end to parse.Describe the solution you'd like The backend API should be reformatting this data and being using query parameters to clearly demarcate the data, ie:
Or something similar. The backend should also handle null cases, not the front end.