Metadata
- Source
- SJRK-453
- Type
- Improvement
- Priority
- Major
- Status
- Open
- Resolution
- N/A
- Assignee
- N/A
- Reporter
- Justin Obara
- Created
2021-02-24T11:26:39.634-0500 - Updated
2021-02-24T11:42:28.227-0500 - Versions
- N/A
- Fixed Versions
- N/A
- Component
- N/A
Description
As part of the work on SJRK-452 the storyId was moved into the model to provide access to the storyId at upload time instead of block creation time. However, this points to a bit of an issue with the ability to direct the path to where the data/files should be sent. It is worth exploring converting the sjrk.storyTelling.block.singleFileUploader.uploadFileToServer into a DataSource and use the idioms provided for supplying a directModel to indicate the exact path for the upload.
It is also worth noting that past discussions have suggested using the infusion uploader instead. If that's the case, the suggestion of converting to a DataSource, as mentioned here, may not be necessary.
Comments
-
Antranig Basman commented
2021-02-24T11:42:28.227-0500 Note that whilst our XHR.send architecture isn't the most brilliantly factored thing in the world, it should be possible to exploit the new "transforming promise chain" DataSource architecture to implement this simply as a further listener slotted into the pipeline.
Note that whilst the `data` argument to this function is documented as a String, there's no reason it couldn't be a FormData instead. Side benefit of a fluidly typed language : P