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
Currently, we are receiving and decoding file-data using input elements and storing blob ref as a Json.Value. We then pass this value around the app, for anybody to use, by encoding and attaching it to a custom element as a property.
This way any other component outside of elm-env may take a file ref and do whatever they want with it.
It would've been nice to migrate away from using input elements to a more explicit and concise API like elm/file, but unfortunately File does not expose its blob-ref and there's no conversion function like File -> Json.Value.
Should there be a way to share a file-ref with the outside-js-code?
The text was updated successfully, but these errors were encountered:
Currently, we are receiving and decoding file-data using
input
elements and storing blob ref as aJson.Value
. We then pass this value around the app, for anybody to use, by encoding and attaching it to a custom element as a property.This way any other component outside of elm-env may take a file ref and do whatever they want with it.
It would've been nice to migrate away from using
input
elements to a more explicit and concise API likeelm/file
, but unfortunatelyFile
does not expose its blob-ref and there's no conversion function likeFile -> Json.Value
.Should there be a way to share a file-ref with the outside-js-code?
The text was updated successfully, but these errors were encountered: