Skip to content

feat: OAuth example flag and per-template verify#27

Merged
Bccorb merged 4 commits into
mainfrom
feat/oauth-usecase-template
Jul 2, 2026
Merged

feat: OAuth example flag and per-template verify#27
Bccorb merged 4 commits into
mainfrom
feat/oauth-usecase-template

Conversation

@Bccorb

@Bccorb Bccorb commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Adds the seamless init --oauth UX and makes seamless verify conformance-test every web template. Pairs with fells-code/seamless-templates#1 (the react-oauth template).

init: use-case example flags

  • seamless init --<alias> (e.g. --oauth) preselects the matching web example from the registry and skips the web prompt. Aliases live in the registry, so new examples need no CLI code.
  • Unknown flags list the available examples; the no-flag web prompt now lists the examples.
  • Adds alias to the registry entry type and a verify block to the manifest type.

verify: conformance for every web template

  • Runs the API and adapter layers once, then builds, serves, and drives each web template from the registry in turn.
  • Each browser run is scoped to the flows the template's manifest declares (verify.flows); react specs are tagged @login / @oauth. A template with no declared flows runs the full suite.
  • The reusable conformance workflow now passes SEAMLESS_TEMPLATES_DIR (the whole checkout) so CI enumerates and tests all web templates. SEAMLESS_REACT_DIR still overrides with a single template.

Validation

  • Full local run against the templates checkout: API/adapter (19) once, then react-vite all-flows (7), then react-oauth @oauth (1). All pass.
  • --oauth preselects the OAuth example and skips the web prompt; unknown flags error with the available list.

Merge ordering

  • Merge feat: add react-oauth use-case template seamless-templates#1 and tag templates v0.2.0 first.
  • A follow-up commit here will bump SEAMLESS_TEMPLATES_REF to v0.2.0 so seamless init --oauth fetches the OAuth example in production. This PR's conformance uses the checked-out templates directly, so it does not depend on the tag.

Bccorb added 4 commits July 2, 2026 18:10
seamless init --oauth (and any registry alias) preselects that web example and
skips the web prompt. Aliases come from the registry, so new examples need no CLI
change; unknown flags list what's available. Adds alias to RegistryEntry and a
verify block to TemplateManifest.
Run the API/adapter layers once, then loop the web templates from the registry:
build, serve, and drive each in turn, scoping the browser suite to the flows its
manifest declares (verify.flows). React specs are tagged @login/@oauth; a template
with no declared flows runs the full suite. SEAMLESS_REACT_DIR still overrides with
a single template (CI path).
Use SEAMLESS_TEMPLATES_DIR instead of a single SEAMLESS_REACT_DIR so the reusable
conformance workflow enumerates the registry and tests every web template.
Makes seamless init --oauth fetch the react-oauth example from the released
templates tag.
@Bccorb Bccorb merged commit cd54381 into main Jul 2, 2026
1 check passed
@Bccorb Bccorb deleted the feat/oauth-usecase-template branch July 2, 2026 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant