-
Notifications
You must be signed in to change notification settings - Fork 79
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
API-First Development #244
Labels
Comments
Hi @pumoica, Besides, if you haven't experience about blueprint development, you could share your nestjs project with design and plugin to develop with that approach. Thanks in advance. |
ghost
added
good first issue
Good for newcomers
question
Further information is requested
labels
Jul 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: