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

Abierto
  • ¿Algo no está bien?
#1,512 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
documentation

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
0
Forks
4
Merge medio
5 h 36 min
PR fusionados (30 d)
509

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Controlvar/controlvar

Todos los issues de Controlvar/controlvar

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.