feat: add i18n category with i18next and next-intl#147
Closed
feat: add i18n category with i18next and next-intl#147
Conversation
Add PythonGraphqlSchema with "strawberry" and "none" options. Wire through all ~30 files: schemas, types, option-metadata, compatibility, CLI index/ prompts/mcp/bts-config/constants/command-handlers/config-processing/ generate-reproducible-command, web builder constant/preview-config/ stack-defaults/stack-url-keys/stack-url-state/stack-utils/tech-icons/ tech-resource-links, smoke test options/presets, and test updates. Template changes: pyproject.toml.hbs adds framework-specific strawberry extras (fastapi/flask/django/litestar), main.py.hbs mounts /graphql route per framework, new graphql_schema.py.hbs with example Query/Mutation types, test_main.py.hbs adds GraphQL hello query tests per framework.
…intl Add i18n as a new TypeScript category supporting two options: - i18next: Universal i18n framework for all frontends (22M+ weekly downloads) - next-intl: Next.js-specific i18n with App Router support Includes full checklist implementation: schema, types, compatibility rules, CLI prompts, web builder, template handler, dep processor, templates, and test/smoke wiring across ~37 files. Compatibility: next-intl is disabled when frontend is not Next.js.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
bot
added
size:L
…defaults Remove two stray closing braces in BASE_LINKS that broke the object literal after the i18n entries were added. Also add i18n to test-utils coreStackFlags and coreStackDefaults so tests don't hang waiting for the new i18n prompt.
Owner
Author
|
Closing — contaminated with cross-PR commits. Will recreate. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
getDisabledReason()rule: next-intl is disabled when frontend is not Next.jsScaffolding verification
4 combos scaffolded and type-checked:
Test plan
bun test apps/cli/test/cli-builder-sync.test.ts-- i18n wiring passes (pre-existing goOrm failure unrelated)--i18n i18nextand verifyapps/web/src/i18n/config.ts+public/locales/generated--i18n next-intl --frontend nextand verifyapps/web/src/middleware.ts+messages/generatednext-intlis disabled in web builder when frontend is not Next.jsbun install && bun run check-typespasses for all 4 combos