Skip to content

Questions: local development #67

@maudnals

Description

@maudnals

I see the (great!) developer guide suggests two ways to experiment with a new feature locally.
You can get started experimenting with the new feature on localhost either by flipping the flag locally or requesting an origin trials token for localhost.

Two questions:

  1. What are pros and cons of the two ways? When would you recommend each approach? What about third-party origin trials, does this change anything?
    Things I could think of:
  • Benefits of localhost tokens over flags:
    • Token can be shared across a team. No need to replace the token when checking out the code of a small prototype (one gotcha though: port- and protocol-dependent)
    • No need to restart the browser / turn flags on and off
    • Work across Chrome and Edge without extra setup
  • Benefits of flags over tokens:
    • Faster to set up
    • Easier to troubleshoot / No troubleshooting: "if a flag is in chrome://flags and I activate it, the feature will be on" (vs.: if I'm using an expired flag, I'll need to troubleshoot this).
  1. Do you think it would be useful to add a brief "When to use flags and when to use a localhost token for local development" in the developer guide under how-can-i-experiment-with-the-new-feature-locally? Or to highlight with a one-liner the one benefit of each approach?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions