Skip to content

feat(mobile-expo): GraphQL client and codegen for Strapi Experience #91

@Ur-imazing

Description

@Ur-imazing

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)

  1. Add @apollo/client and optionally @forge/graphql as workspace dependency; ensure Metro resolves workspace packages.
  2. Or: dedicated codegen script in mobile/expo that reads schema and outputs types/hooks (e.g. graphql-codegen or similar).

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions