Skip to content

feat: add codegen generator fixtures (TON-850)#446

Open
nikdim03 wants to merge 1 commit into
mainfrom
feature/ton-850-codegen-fixtures
Open

feat: add codegen generator fixtures (TON-850)#446
nikdim03 wants to merge 1 commit into
mainfrom
feature/ton-850-codegen-fixtures

Conversation

@nikdim03

@nikdim03 nikdim03 commented Jun 2, 2026

Copy link
Copy Markdown
Contributor

Lands the JSON-Schema-generator fixture (model-patterns.fixture.ts) on main — the part of the closed #364 the reviewer asked to keep (the rejected generate-json-schema.spec.ts is intentionally not included).

Why: the iOS and Android codegen-result tests (make models / generate-test-models.sh → diff generated models against the committed snapshot) need this fixture as their input. With it only living on the abandoned feature/ton-850-schema-generator-tests branch, both platforms had to pin CI to a dead branch. Landing it here lets them point at main.

Scope: single fixture file; the generator scripts it feeds (generate-json-schema.js, json-schema-to-openapi-spec.js) are already on main.

Adds model-patterns.fixture.ts, the JSON-Schema-generator fixture covering
every TypeScript→JSON Schema pattern handled by generate-json-schema.js.

Lands the fixture on main (the part of the closed #364 the reviewer asked
to keep) so the iOS and Android sides can generate models from it and test
the generated output, instead of pinning CI to the abandoned feature branch.
@vercel

vercel Bot commented Jun 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
kit-demo-wallet Ready Ready Preview, Comment Jun 2, 2026 2:59pm

Request Review

@coderabbitai

coderabbitai Bot commented Jun 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@nikdim03, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 56 minutes and 59 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: dc082886-7331-4c9a-8fd2-76bd93f519a5

📥 Commits

Reviewing files that changed from the base of the PR and between 18474c3 and a75d323.

📒 Files selected for processing (1)
  • packages/walletkit/src/api/scripts/__fixtures__/model-patterns.fixture.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/ton-850-codegen-fixtures

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

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