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

Add JHipster.NET #677

Open
nicolas63 opened this issue May 1, 2020 · 0 comments · May be fixed by #678
Open

Add JHipster.NET #677

nicolas63 opened this issue May 1, 2020 · 0 comments · May be fixed by #678
Assignees

Comments

@nicolas63
Copy link

  1. Have your repository in Github or any source control been created at least 3 months?

We review by going to your repository to verify the first file you're created, but the process might take time so please help to declare here, then it will be easy for all reviewers

https://github.com/jhipster/jhipster-dotnetcore

  1. The reason you think your library/framework/tooling/link is awesome?

This is to prevent some of library or framework is too small in size and famous level which help this awesome list becomes a reliable references for .NET community

The goal main generator of jhipster is showcases best practices of modern web development in java. So the goal of the project is to do the same in .net. We keep the front in angular or react and the back is in asp.net core
Sample app generated : https://github.com/jhipster/jhipster-sample-app-dotnetcore

  1. Have your PR follows up with alphabet-ordering?

Help to strictly check the alphabet-ordering before you submit the PR so that will be helpful for .NET Community easy to find the library/framework/tooling/link that they need

  1. Is it .NET Core or .NET Standard?

The generated app is in .net core with .net strandard library

  1. Have you read through the README or issues list to make sure that your PR is not duplicated to any others?

YES, my PR is unique.

@nicolas63 nicolas63 linked a pull request May 1, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants