You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the JHipster options is "API-First Development" (https://www.jhipster.tech/doing-api-first-development/) provides great benefits (mentioned in the link) and our team has been extensively using it for our java-based (micro)services.
Arguably, the most significant benefit is using this option enforces a team to really think well (and do so before writing code) about how exactly services are going to interact. This adjustment in our SDLC helps a lot in preventing many issues downstream that are a consequence of treating your service API as rather an afterthought and/or a "convenience" of your service implementation.
We've started adding new services (to our solution) that are based on NestJS framework and were excited to see the node version of JHipster but it seems that NHipster does not have the mentioned option implemented.
Are there any plans to add this option anytime soon?
Apologies if the feature is already in place and I simply missed it.
The text was updated successfully, but these errors were encountered:
Hi @pumoica,
thanks for the interest!!
In this moment NHipster does not support api-first development feature.
If you want to contribute for it, you are welcome!!
Besides, if you haven't experience about blueprint development, you could share your nestjs project with design and plugin to develop with that approach.
One of the JHipster options is "API-First Development" (https://www.jhipster.tech/doing-api-first-development/) provides great benefits (mentioned in the link) and our team has been extensively using it for our java-based (micro)services.
Arguably, the most significant benefit is using this option enforces a team to really think well (and do so before writing code) about how exactly services are going to interact. This adjustment in our SDLC helps a lot in preventing many issues downstream that are a consequence of treating your service API as rather an afterthought and/or a "convenience" of your service implementation.
We've started adding new services (to our solution) that are based on NestJS framework and were excited to see the node version of JHipster but it seems that NHipster does not have the mentioned option implemented.
Are there any plans to add this option anytime soon?
Apologies if the feature is already in place and I simply missed it.
The text was updated successfully, but these errors were encountered: