Replies: 1 comment 1 reply
-
This is actually already the case - if you look at the content in that step, https://livepeerjs.org/examples/react/ipfs-playback#step-2-automatic-playback, it indicates:
This is only used to ensure that the UI input is valid. We can tweak the example code, since this is technically just shown for UI purposes in the docs (to show that the input is valid/invalid). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The current code example for IPFS playback at https://livepeerjs.org/examples/react/ipfs-playback requires the dev to import
parseCid
fromlivepeer/media
which needs to be called and the value passed to the Player.Got some feedback that it would nice to go one step further and have a way to hide
parseCid
from the dev by default so that they have a way to just input an IPFS URL into a component and theparseCid
logic is auto-executed by the component internally without exposing that function to the dev. Maybe a wrapper component around the Player that just takes the IPFS URL?Beta Was this translation helpful? Give feedback.
All reactions