Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.Net blueprint cannot be released due to modularization specifics. #27764

Closed
1 task
mshima opened this issue Nov 1, 2024 · 0 comments · Fixed by jhipster/jhipster-dotnetcore#1526
Closed
1 task
Assignees
Labels
area: bug 🐛 $$ bug-bounty $$ https://www.jhipster.tech/bug-bounties/ theme: blueprint 🐾 $500 https://www.jhipster.tech/bug-bounties/
Milestone

Comments

@mshima
Copy link
Member

mshima commented Nov 1, 2024

Overview of the issue

.Net blueprint generates a quite different structure.
JHipster modular support needs adjusts.

Java based projects:

- package.json
- src/main/webapp (client)
- src/main/docker (docker)
- * (java)

.Net:

- package.json (husky and prettier that needs to be in git root)
- src/Jhipster/ClientApp (client)
- src/Jhipster/ClientApp/package.json (client dependencies/eslint)
- src/* (dotnetcore)
- test/* (dotnetcore)

There are 2 package.json to be considered: at root and at client folder.

Currently if the dependency is in package.json templates it will be written to client's package.json and if the dependency is injected it will be written to root's package.json.
Same for scripts.

We should add an api to write to client's package.json and adjust insertions.

Browsers and Operating System
  • Checking this box is mandatory (this is just to show you read everything)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: bug 🐛 $$ bug-bounty $$ https://www.jhipster.tech/bug-bounties/ theme: blueprint 🐾 $500 https://www.jhipster.tech/bug-bounties/
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants