TV Show Project Level 500: Build a front page
维护者通常 10 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- javascript
- 领域
- frontend
调研方向
先查看 README.md 了解仓库的提交说明，然后检查原始代码库和 level 500 的要求。当 shows 列表、show 搜索、导航、剧集控件以及 one-fetch-per-URL 行为能够协同工作，并且所需的经合作伙伴审查的 pull request 已准备就绪时，工作即完成。
由索引模型根据 Issue 内容生成。
描述
Level 500
For level 500, you should switch back to your original codebase.
You should have reviewed and merged someone else's level 400 implementation.
Once again, compare their implementation to yours. Think:
- How is it different?
- What do you prefer about your implementation?
- What do you prefer about their implementation?
- What did you learn that you didn't know before?
Have a discussion about your answers to these questions. In class, together you should give a 3 minute talk about your conclusions.
Refactoring
Feel free to change anything in your codebase which you think will make it easier to work with, or to build new features.
Make a branch and pull request for yourself, and then have your partner review, making sure they understand the changes made.
Adding new functionality
Level 500 is about adding a front-page which lets users select (and find) shows from your shows list.
Requirements
- When your app starts, present a listing of all shows ("shows listing")
- For each show, you must display at least name, image, summary, genres, status, rating, and runtime.
- When a show name is clicked, your app should:
- Fetch and present episodes from that show (enabling episode search and selection as before)
- Hide the "shows listing" view
- Add a navigation link to enable the user to return to the "shows listing"
- When this is clicked, the episodes listing should be hidden
- Provide a free-text show search through show names, genres, and summary texts
- Ensure that your episode search and episode selector controls still work correctly when you switch from shows listing to episodes listing and back
- During one user's visit to your website, you should never fetch any URL more than once.
Screenshot of minimal version
Note: Provided your project meets the above requirements, it can look however you want.
Here is one example layout.
Submission
Once you have finished your level 500 it is ready to submit.
Check the README.md for this repo for instructions.
- 主要语言
- JavaScript
- 星标
- 0
- 派生
- 276
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
CodeYourFuture/Module-Data-Flows 的其他 Issue
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Data-Flows Submit:None 🦔 Size Tiny
难度 1/5 1 小时以内 新手友好度 85/100
CodeYourFuture/Module-Data-Flows#485 ·
维护者通常 10 天内回复
-
🏕 Priority Mandatory 🐇 Size Small 📅 Sprint 2 Core Module-Data-Flows Submit:None
难度 1/5 1 小时以内 新手友好度 72/100
CodeYourFuture/Module-Data-Flows#484 ·
维护者通常 10 天内回复
-
🏝️ Priority Stretch 📅 Sprint 1 📅 Sprint 2 📅 Sprint 3 Optional Recurring Submit:None
难度 1/5 1 小时以内 新手友好度 25/100
CodeYourFuture/Module-Data-Flows#590 ·
维护者通常 10 天内回复
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 3 Core Module-Data-Flows Submit:None
难度 2/5 1-3 小时 新手友好度 35/100
CodeYourFuture/Module-Data-Flows#373 ·
维护者通常 10 天内回复
-
🏕 Priority Mandatory 🐂 Size Medium 📅 Sprint 2 Core Module-Data-Flows Submit:None
难度 2/5 1-3 小时 新手友好度 35/100
CodeYourFuture/Module-Data-Flows#372 ·
维护者通常 10 天内回复
查看 CodeYourFuture/Module-Data-Flows 的全部 Issue
相似的 Issue
-
external-issue to-triage
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
LearningCircuit/local-deep-research#7067 ·
维护者通常 1 天内回复
-
automated issue report
难度 1/5 1 小时以内 新手友好度 65/100
lirantal/discoprint#32 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复