Site video: a flag that serves a string, number or JSON value

未关闭
  • 哪里不对？
#1,512 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
15/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
documentation

调研方向

Start with the showcase constraints in tests/acceptance/showcase/contract.py, especially MAX_VIDEO_MS (55-90 s), and the capture gates that check narration against real product answers. The first deliverable is a written plan for the new video, which needs review before any build. The video waits on the #1497 dashboard work merging, and the optional results segment also waits on #1496. Done means the voiced final passes every gate at the release tag and is approved and published before the launch announcement.

由索引模型根据 Issue 内容生成。

描述

A new short site video should show a flag that serves a value rather than on or off, the one new dashboard journey among the launch items. It must be published before the launch announcement.

None of the seven site videos becomes wrong because of the launch items. Videos 01, 02 and 06 show results pages that will gain an interval on the lift and the incremental impact (#1496). Video 03's New Flag form will gain a "Type" choice, which defaults to today's on/off behaviour. Neither change is shown anywhere today.

What the video should show

  1. Creating a flag that serves a string, a number or a JSON value (#1497): choose its type, set the value served to the users the flag is on for and the value everyone else gets, then turn it on.
  2. Who gets which value: a targeting rule and the rollout percentage decide it, and turning the flag off serves the off value to everyone.
  3. Reading the value in an application through an SDK (getStringValue or the equivalent), if the capture can show it.

Optional, decided in the plan: a short results segment showing the interval on the lift and the incremental impact (#1496), either in this video or as a separate one.

Known constraints

  • It records the dashboard as it ships, so it waits for #1497's dashboard work and, for the optional segment, #1496's results screens to merge.
  • The showcase capture tool records the browser only.
  • Every video is held to 55-90 s (MAX_VIDEO_MS in tests/acceptance/showcase/contract.py) unless the plan gives it its own limit.
  • The narration may only say what the video shows and what a test pins, as for every other video.

Done when

  • The capture's gates check what the video says against the product's real answers.
  • The voiced final at the release tag passes every gate.
  • The final is approved before it is published, and it is on the site before the launch announcement.

A plan comes first. Nothing is built before it is reviewed.

主要语言
Python
星标
0
派生
4
平均合并
5 小时 36 分钟
30 天内合并 PR
509

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

Controlvar/controlvar 的其他 Issue

查看 Controlvar/controlvar 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。