Skip to content

fix(cli): store generated project settings with the project - #140

Merged
ItayTheDar merged 2 commits into
mainfrom
fix/project-local-cli-settings
Sep 28, 2026
Merged

ItayTheDar merged 2 commits into
mainfrom
fix/project-local-cli-settings

Conversation

@ItayTheDar

@ItayTheDar ItayTheDar commented Sep 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Fixes #41. Generated apps now write settings.yaml to their own root instead of the installed PyNest package. CLI generation reads project-local settings from the current directory or an ancestor, so separate projects keep independent database/CLI choices.

The test dependency group now requests sqlalchemy[asyncio], fixing CI collection with SQLAlchemy 2.1 (which requires greenlet).

Verification

  • CI-equivalent uv sync --no-dev --group test followed by pytest -q tests: 205 passed
  • Separate CLI processes generated an async SQLite app and resource; imported the generated app and received HTTP 200 from GET /
  • git diff --check: clean

The existing Black configuration has an invalid force-exclude regex, so its project-config check cannot run; checking with an empty config finds only pre-existing formatting in generate_service.py outside this diff.

@ItayTheDar
ItayTheDar merged commit ae83aaa into main Sep 28, 2026
28 checks passed
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.

Create settings.yaml if not found in Module Creation

1 participant