Marcelo Shima
Marcelo Shima
No plans for typescript blueprints in official blueprints and generate-blueprint command. I don’t see any advantage in adding the typescript complexity in blueprints. But it’s possible to create a typescript...
We should add an option `extension` with 'js' and 'mjs' options, which will default to 'mjs' for local blueprint and 'js' otherwise.
Only add/remove field is supported. Field rename and field attributes change are not supported. There is no plan to support.
I’ve tried to add the test, but failed. Maybe related to how vitest handles it.
@dependabot rebase
I think that a gradle catalog is easier to maintain instead of a pom.xml. https://github.com/jhipster/generator-jhipster/blob/main/generators/server/resources/gradle/libs.versions.toml
@emilpaw please continue witth pom.xml. Gradle catalog have the entire dependency info in a single line while pom structure is more complex. It’s just for information.
cc @colameo is this difficult?
Please provide a full jdl with application in the issue description.
``` import { createEnv } from 'yeoman-environment'; await createEnv().run(['path/to/generator.js']); ```