Integrate VueJS blueprint as a mainline generator (like Angular and React) #10575
Comments
|
It's an important discussion |
|
I'm ok for merging Vue, the blueprint is quite stable and very well made :) Just one thought about that quote:
Both 3 frameworks are made to build applications, if you do shitty things with Angular, ofc the app will suck, same goes for Vue and React. I agree that Vue is great etc, I even use it myself for small personal projects, but don't discard other technologies because they do have less Github stars or less representation in articles, that doesn't mean anything. I would have said the same for React of course. |
|
I do a lot of presentations to Java developers around the world. In my opinion, that's the target audience for JHipster. I usually survey the audience to see what frameworks they're using. Angular and React are usually tied in the number of users they have. Vue.js is hardly used by anyone in comparison. Usually just 2-3 hands go up.
IMO, Twitter and the internet (+ who you follow) make Vue seem popular, but it's enterprise usage is still quite low.
… On Oct 8, 2019, at 08:22, William Marques ***@***.***> wrote:
I'm ok for merging Vue, the blueprint is quite stable and very well made :)
Just one thought about that quote:
VueJS is really gaining popularity, it really makes sense to do it. Some recent articles are now only comparing React and VueJS, Angular is no more part of the comparison :-(
Both 3 frameworks are made to build applications, if you do shitty things with Angular, ofc the app will suck, same goes for Vue and React.
Both have pros/cons, I always see the 3 frameworks on "comparison articles".
Angular is very widely used especially in the Java ecosystem.
I agree that Vue is great etc, I even use it myself for small personal projects, but don't discard other technologies because they do have less Github stars or less representation in articles, that doesn't mean anything.
I would have said the same for React of course.
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I don't want to compare those technologies here. I am just talking about popularity. I hate React, and yet it is the mostly widely used :)
Ok that is interesting. However, do you make presentation really worldwide, or mostly Europe for instance? You are right, big compagnies use a lot Angular and React, but I think that lots of startup opt for VueJS, because much lighter to start with. And I think that JHipster is very useful for startup who wants to start really fast... Big companies develop their own ecosystem. That is my opinion of course ;) |
|
My presentations this year have been in North America, Europe (Spain, UK, and Ireland), and India. I hope to add Australia, Japan, and more Asian countries in 2020. Do you hate React because you used it on a project and it failed or because you don't like how it works? Just curious as to where your bias comes from. Personally, I like all three frameworks. |
I (tried to) use it only personally. I hated it because I found tons of boilerplate code, 10.000 ways to do the same things (I guess it leads to very messy projects), and not very abstract... I was happy to see some other people were also allergic to it as well ;) |
Big companies also use JHipster a lot. |
|
I'm ok with merging the blueprint. I don't think we have any reason to do comparisons and stuff. In general, React is the most popular lib followed by Vue and Angular, but within the JHipster community usage of Vue might be less. I personally like React followed by Vue, Angular is kind of loosing out to these. For now, it makes sense to offer all 3 options |
|
I believe we should also consider maintenance overhead. I have observed less community interest to maintain |
|
It would ge good to have vue in the main generator, but currently I see one huge issue with that. It is the protractor for e2e testing. We always try to follow best practices and choose the best tool for the job but in that case I think we could do better from a vue point of view. So first we need to update the blueprint and get our ci up and running reliable again before continuing here. In general regarding the fact jhipster online does not support the official blueprints I currently don't see a huge issue with that, but when node, .net and maybe micronaut gain traction it would be awesome to select them in jhipster online too. |
That's what I am concerned about. I see no/little active participation by the community to fix broken builds. If we think that the migration to On a personal note, I also think about moving |
|
For me, it's the way to go to. so +1. |
|
@vishal423 I think the reason is that we have more people in the core team interested in Angular than React. Earlier I was the one maintaining React as I built that part but then later there were few others. But IMO React is still a better option than Angular. |
|
If protractor is becoming a bottleneck, then may be lets reconsider moving to Cypress |
|
Hi everyone ! I'm not sure that the main concern here is Protractor, but the increasing complexity of combinations offered by JHipster. Just to let you know, I tried to create a module for Cypress, but was blocked with two issues:
I also wanted to focus more on prettier-java so I stopped working on this lately, but I would like to work further with this in the future. PS: here is my repo, for those interested: https://github.com/clement26695/generator-jhipster-cypress |
|
@deepu105, that was my personal opinion after working on both Supporting multiple front end implementations might impact/delay introduction of new features on backend. As an example, if we plan to support aggregates, then, those would also require UI changes on |
I totally agree we need to be careful with this point.
I think it becomes out of the topic. Fixing e2e tests is a prerequisite, fine. I am not very familiar with e2e tests in JHipster: are they all the same, or do they depend on Angular/React? Would a requirement be that we would prefer Cypress over Protractor only for VueJS? Shouldn't we focus on "technical" requirement instead of technical problems themselves? |
|
If Cypress makes our e2e more stable then I'm fine to move to it fully.
Ideally we should have same e2e test suite for all framework. Thats why we
put in effort to render the sme final HTML from Angular and React. We
should do the same for vue as well, it means using same id, name, class
names and structure. So that we can use the same e2e test templates for all
of them
Thanks & Regards,
Deepu
…On Wed, Oct 9, 2019 at 12:11 PM Christophe Moine ***@***.***> wrote:
I'm not sure that the main concern here is Protractor, but the increasing
complexity of combinations offered by JHipster.
I totally agree we need to be careful with this point.
If protractor is becoming a bottleneck
I think it becomes out of the topic. Fixing e2e tests is a prerequisite,
fine. I am not very familiar with e2e tests in JHipster: are they all the
same, or do they depend on Angular/React? Would a requirement be that we
would prefer Cypress over Protractor only for VueJS? Shouldn't we focus on
"technical" requirement instead of technical problems themselves?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10575?email_source=notifications&email_token=AAIOKF3FNUUKPSB42A77NXLQNWU4HA5CNFSM4I6RKRIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAXMDGI#issuecomment-539935129>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAIOKF2ZUWT2N76CVGZA3H3QNWU4HANCNFSM4I6RKRIA>
.
|
|
I just did a VueJs app and really loved it. For my personal use, this would be my favorite framework today, so I'd be happy to see this merged. |
|
+1 for the idea, -1 for having to slog through a bunch of comments that amounted to "The framework that I like is better than the framework you like". |
|
I would very much like to see VueJS integrated into the main project. Vuejs is gaining popularity and is very easy to use. It would also be ideal to have the option of choosing any of the three frameworks (angular / react / vuejs). I hope it can be posible. I would also like to see kotlin integrated in the main project |
|
vue 3.0 Pre-Alpha has been released. is it the time to integrated vue 3.0 into the main project? |
|
No, the migration to vue3 won't be done as it is still in alpha |
|
I really love the idea of putting all three frameworks in the main generator. My only concern is about the overhead that it will add (both in maintaining it and to our pipelines). I think we can wait a bit to see whether the usage of VueJS (within JHipster context) goes beyond a certain level (like more than 25% users) use VueJS. Then we can decide on moving that into the main generator. A fun hacktoberfest idea: The prompts should intelligently fetch options from the official blueprints. This will enable us to add |
|
I would argue that vue is already overtaking react while still being a blueprint which is impressive !
As for dynamically adding options, it's obviously not feasible as a new version of the core can break blueprints (and often does). Also if it is in the official prompt why not move the code to the core repo so that we can end to end test it and prevent regressions. |
|
The last part was done, related to daily builds :
We can close this ticket |
|
The bounty has been claimed at https://opencollective.com/generator-jhipster/expenses/22609 |
|
Great work Pascal! 👍🎉 |
|
Thanks a lot @atomfrede ! |
|
Great work Pascal. You rock
…On Sun, 26 Jul 2020, 10:32 pm Pascal Grimaud, ***@***.***> wrote:
Thanks a lot @atomfrede <https://github.com/atomfrede> !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIOKF7SPR2ZY2TLJWRBWO3R5SHERANCNFSM4I6RKRIA>
.
|
|
Any possible to support Vuetify? Seems vuetify is a better solution on Vue.JS |
|
@alaahong vuetifyjs is a very good option I always use it in my projects with jhipster (Of course making a lot of changes to the UI). I would like to create a blueprint to integrate vuetify once jhipster version 7 comes out and analyze all the changes that come in this new version. I think I will need a lot of help especially in the tests |
|
We won't be supporting any other UI frameworks. We use bootstrap on React
and Angular and will use the same for Vue.
If you like another UI the best way is to make it a blueprint
…On Sun, 9 Aug 2020, 7:00 pm Yuniel Acosta Pérez, ***@***.***> wrote:
@alaahong <https://github.com/alaahong> vuetifyjs is a very good option I
always use it in my projects with jhipster (Of course making a lot of
changes to the UI). I would like to create a blueprint to integrate vuetify
once jhipster version 7 comes out and analyze all the changes that come in
this new version. I think I will need a lot of help especially in the tests
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10575 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIOKF4QACENWQIZNA7HBUTR73I2JANCNFSM4I6RKRIA>
.
|
and others
Overview of the feature request
The actual flow for VueJS is awkward (CLI and https://start.jhipster.tech/#/generate-application as well):
Moreover the web site claims:
Spring Boot + Angular / React / Vue Web applications
I think it is very frustrating/confusing that we cannot choose VueJS instead of React/Angular. I am pretty sure some users just give up after that and do not dig deeper.
Motivation for or Use Case
VueJS is really gaining popularity, it really makes sense to do it. Some recent articles are now only comparing React and VueJS, Angular is no more part of the comparison :-(
Moreover, I think the VueJS generator would gain popularity and stability since it would be part of the release train. At the moment, a new JHipster version does not imply the blueprints have been tested against it (from JHipster perspective) (tell me if I'm wrong).
Related issues or PR
None, but I would be glad to contribute for this feature in a PR.
The text was updated successfully, but these errors were encountered: