Skip to content

fix(node-server): generator-jhipster at 7196a350, the docker:db scripts of SQLite and oauth2AppSchemes of the JDL from JHipster - #1606

Merged
DanielFran merged 2 commits into
jhipster:mainfrom
mshima:sqlite-docker-db-scripts
Nov 5, 2026
Merged

DanielFran merged 2 commits into
jhipster:mainfrom
mshima:sqlite-docker-db-scripts

Conversation

@mshima

@mshima mshima commented Nov 3, 2026 •

Copy link
Copy Markdown
Member

generator-jhipster at 7196a350 of main, with two fixes the blueprint takes from it.

The docker:db scripts of SQLite. The docker generator of the blueprint removed the docker:db:up/docker:db:down scripts for a SQLite production database: JHipster wrote them for any SQL database, without the docker file of its service, so docker:db:up ran a docker compose -f src/main/docker/sqlite.yml that does not exist. jhipster/generator-jhipster#35964 writes them only when the database is one of the docker services, like any other database: SQLite gets a docker:db:up that echoes that docker is not configured for it, and no docker:db:down.

  • The sqliteDatabaseScripts task of the docker generator is removed.
  • The spec of node-server with prodDatabaseType: sqlite checks the echo and that there is no docker:db:down.

oauth2AppSchemes of the JDL. oauth2AppSchemes, the URL schemes of the apps (like mobile apps) signing in at the OAuth2 provider, was refused by the JDL of a NodeJS application ("Unknown application option: oauth2AppSchemes"): JHipster declared it in its server command, which the server command of the blueprint replaces, so the Keycloak realm got no redirect URI of the apps. jhipster/generator-jhipster#35972 declares it in the docker command of JHipster, the generator writing the realm, which its spring-boot command imports.

  • The node-server command of the blueprint imports docker too, so the JDL knows the option, without a copy of it in the blueprint.

The client snapshot has the two pagination files the client of main now writes (pagination.ts, pagination.spec.ts).

Tested

  • Blueprint specs (160) and eslint pass, on generator-jhipster 7196a350.
  • An OAuth2 application with oauth2AppSchemes [myapp, exp] in its JDL (generated like the jdl command of the cli): the option kept in .yo-rc.json, myapp:* and exp:* among the redirect URIs of the client of the Keycloak realm (docker/realm-config). Without the import of docker, the same JDL is refused with "Unknown application option: oauth2AppSchemes".

Not tested locally: the CI samples (monolith-react-sqlite-prod-jdl, and the SQL samples whose scripts now come from the condition of the docker services; none has oauth2AppSchemes); the CI runs them.

🤖 Generated with Claude Code

@mshima
mshima marked this pull request as ready for review November 3, 2026 13:41
…tes them only for a database of the docker services

generator-jhipster at a2666ea7 of main.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mshima
mshima force-pushed the sqlite-docker-db-scripts branch from 3058a98 to 459de3c Compare November 3, 2026 16:37
…d of JHipster the server imports

generator-jhipster at 7196a350 of main declares oauth2AppSchemes in its docker command: the node-server command imports
it, so the JDL of a NodeJS application keeps the URL schemes of its apps, redirect URIs of its Keycloak realm.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mshima mshima changed the title fix(docker): the docker:db scripts of SQLite from JHipster, which writes them only for a database of the docker services fix(node-server): generator-jhipster at 7196a350, the docker:db scripts of SQLite and oauth2AppSchemes of the JDL from JHipster Nov 3, 2026
@DanielFran
DanielFran merged commit a09e8fa into jhipster:main Nov 5, 2026
35 checks passed
@mshima
mshima deleted the sqlite-docker-db-scripts branch November 5, 2026 18:55
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.

2 participants