Joystream / Joystream/joystream
Content directory smart contracts: Featured videos
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Assuming this is simply a set of references to existing videos we could just have a set of methods to support actions currently available through CLI (executable only by the lead):
setFeaturedVideos(_videoIds[])addFeaturedVideos(_videoIds[])removeFeaturedVideos(_videoIds[])
The contracts don't need to store any additional data here, they can just emit an event to be handled by query node.
Featured header video
Here we may need an additional metadata, persumably related to the displayed preview (ie. timestamp boundries).
I don't think there would be any need to store any of this data in the contracts either, so it seems that a simple method like setFeaturedHeaderVideo(_videoId, _metadata) would be enough (leaving metadata processing to query node)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing CLI actions for featured videos and the current smart-contract and query-node conventions. Define how the proposed methods, lead-only access, emitted events, and header-video metadata should integrate; done means the contract interface supports featured videos and the query node can handle the resulting events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100