Klaudiusz Dembler
Klaudiusz Dembler
Yes, we tried that. The issue is that like I said we would like to avoid having styles based on the `.lf-player-container` class in our codebase as we may want...
> YPP is just about done, end-to-end Well I wouldn't say that's 100% accurate. While most of the tickets we've drafted for Atlas are done, there definitely needs to be...
It's not that painful since the functionality offered by the library isn't that complex and there's only a handful of functions but it's still nice to have. With typings: -...
#23 is certainly a good start but I'd say there's still more work to be done to close this issue. #23 provides basic types that `tsc` can infer on its...
1. Re app metadata: looks good but not sure why distinction between `platform` and `versions` is necessary. Maybe I'm misunderstanding but I would just go with a single `platforms` entry...
Looks good to me then!
> Well, the on-chain db in particular the content pallet model wasn't designed with this feature in mind (assets 1:1 files, not 1:n) and it is unlikely a change like...
When you create a video or a channel, one of the extrinsic args is `meta: Bytes`. This blob of bytes is never accessed by runtime and only used by QN....
Once we do this change I guess we could use similar approach for serialized metadata as we've discussed for https://github.com/Joystream/joystream/issues/3255 so that we can identify different types of content
What worked as a workaround for me was using a relative import inside the monorepo instead of absolute package paths. So assuming you have a monorepo with `app/` and `plugin/`...