Skip to content

chore: update generated files from PR #11467#36

Open
loyaltylion-bot wants to merge 1 commit into
mainfrom
codegen/pr-11467
Open

chore: update generated files from PR #11467#36
loyaltylion-bot wants to merge 1 commit into
mainfrom
codegen/pr-11467

Conversation

@loyaltylion-bot

Copy link
Copy Markdown
Collaborator

Auto-generated by the CI pipeline.

Source: https://github.com/loyaltylion/hogwarts/pull/11467

These files were regenerated from changes to the API contracts. Review and merge alongside the main PR.

Generated files:

  • src/types/api.ts
  • src/types/schemas.ts

@loyaltylion-minerva loyaltylion-minerva Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The generated OpenAPI/schema changes are internally consistent, but the new country-aware request contract is not exposed through the package's primary createHeadlessApiClient wrapper. Consumers using the documented client cannot pass country to configuration/customer/reward/rule calls, so country availability filtering will silently keep using the site default.

Comment thread src/types/api.ts
language?: unknown;
language?: string;
/** @description ISO 3166-1 alpha-2 country code for the customer. Used to filter rewards by country availability. If not provided, the site default is used */
country?: string;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This new country query parameter is generated across the Headless operations, but the public wrapper in src/client.ts still has no country option and all wrapper calls only send path params. That means consumers using the documented createHeadlessApiClient API cannot request a non-default country, so country availability filtering for configuration, customer state, reward redemption, and rule completion remains unreachable unless they bypass the wrapper and call the raw OpenAPI client/fetch path themselves. The generated contract should be paired with wrapper support, for example a client-level country?: string that is threaded into each request's params.query.

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