Marcelo Shima
Marcelo Shima
Still an issue
Snapshots are not been generated. Closing since we are generating applications with released bom instead of snapshots now.
I don't think we should make `jhipsterConfig` typed. - blueprints will need to convert to any before using.
`jhipsterConfig` and `jhipsterConfigWithDefaults` are never manually used anymore. Command has evolved as somewhat source of truth. https://github.com/mshima/generator-jhipster/blob/f0a8e84e2fbd24ab2f7e9cbe2bcac581004aa671/generators/git/command.ts#L37-L39 A storage scoped config: - allows cli option/argument with choices - allows prompts...
I think we should generate Types from command instead of reworking types see https://github.com/jhipster/generator-jhipster/pull/27133.
New entities added new code and increased complexity, the sonar error is not blocking.
@OmarHawk readonly is quite uncommon use case. This looks related to https://github.com/jhipster/generator-jhipster/issues/25414 Use saveAndFlush for jpa and entity with fields that requires flush like `@AutoGenerated`? Not sure it’s possible to...
Add readonly to typescript type?
[Reopen] The default profile is ignored when rebuilding an application generated with Jhipster 8.6.0
Happened in a vscode rebuild with me. I wonder if it’s a IDE misbehavior.
[Reopen] The default profile is ignored when rebuilding an application generated with Jhipster 8.6.0
> Any idea for a workarond? I use wsl and vscode fits perfectly. No, probably duplicate the maven-resources-plugin configuration instead of rely on parent pom configuration.