-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Description
Background
The Expo watch app must fetch content from Strapi via GraphQL (same Experience and section model as web). This issue adds the GraphQL client and codegen so the app can query Experience(s) by slug/locale and use typed section data.
Expected outcome
- Apollo Client (or chosen client) wired to the Strapi GraphQL endpoint (configurable per environment).
- Typed operations for Experience(s): watch home (homepage) and experience-by-slug with locale.
- Section fragments or types aligned with
apps/cms/schema.graphql(MediaCollection, PromoBanner, InfoBlocks, CTA). - Codegen from
apps/cms/schema.graphql—either reuse@forge/graphql(if Metro-compatible) or Expo-specific codegen.
Acceptance criteria
- GraphQL client configured with endpoint from env (dev/stage/prod).
- Codegen produces types/operations from
apps/cms/schema.graphql. - At least one query for experiences (e.g. by slug and locale, or homepage).
- No hand-editing of generated output; regeneration documented.
Possible solution(s)
- Add
@apollo/clientand optionally@forge/graphqlas workspace dependency; ensure Metro resolves workspace packages. - Or: dedicated codegen script in
mobile/expothat reads schema and outputs types/hooks (e.g. graphql-codegen or similar).
References
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done