code.quarkus.io extension ordering
Guillaume Smet
Stuart Douglas
Anyway, food for thoughts.--Guillaume
--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo8ADniRe0tSBnqC0JqDsh7TGKRDwjhF%2Bb_VZp_XOBUwAQ%40mail.gmail.com.
Max Rydahl Andersen
Hi,
I don't really have an idea about how to fix it but I thought maybe just
acknowledging the issue collectively could be a good idea and might help to
get ideas in shape.When going to https://code.quarkus.io/ , the order of extensions is very
confusing:
- some of them are at the top as we thought they would be the most commonly
used so it's not a purely alphabetical order
- then we have a bunch of extension in alphabetical order, which
unfortunately for some of the extensions is not very natural.
Some of the problems I identified:
- Eclipse Vert.x GraphQL at the very top. Not with the other Vert.x
extensions and the first one to mention GraphQL, whereas maybe we would
like to push users to SmallRye GraphQL - I noticed that because I was
surprised somebody reported an issue with it, I would have expected people
to use the SmallRye stuff in priority
make smallrye graphql sticky so it shows up sooner ?
- Related extensions being split so no good way to know you have a choice
(typically the JAX-RS Client Reactive extension coming as the 6th one,
totally split from the REST Client Reactive one, which should be used in
priority)
- JDBC Driver Oracle lost in the middle and not with the other JDBC drivers
(that one is an easy fix, I will fix it right away)
Given how many extensions we have (and more coming if we start including
the Quarkiverse...),
This is one of the reasons we won't add quarkiverse by default in the list on code.quarkus -
the platform will be first and only when searching would it show quarkiverse options.
That limits the "chaos" at least.
it's not really easy to order them but my guess is
that we need some semantic grouping to guide the users and show them the
alternatives they have. It might not be easy as some extensions might be
related to several semantic groups.
yeah - the list is just too long and I don't think there is much sense in keeping showing the long list imo. But its what we have
for now and we have ability to "pin" per category and also hide extensions if deemed "too" internal.
Once optional dependencies are fully used we should be able to hide all technical binding extensions.
Last we looked at this was when we came up with the idea of "groups" which would be a preselection of common usecases which
would be on top of the code.quarkus (and IDEs in future). James Cobb made a mockup of it and got fairly good feedback -
it was put on hold until we got the registry and external extensions to show up.
I tried find the issue with the attached mockups but not finding yet - i'll see if James can digg it out and share here.
/max
Anyway, food for thoughts.
--
Guillaume
--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo8ADniRe0tSBnqC0JqDsh7TGKRDwjhF%2Bb_VZp_XOBUwAQ%40mail.gmail.com.
/max
https://xam.dk/about
Andy Damevin
Last we looked at this was when we came up with the idea of "groups" which would be a preselection of common usecases which
would be on top of the code.quarkus (and IDEs in future). James Cobb made a mockup of it and got fairly good feedback -
it was put on hold until we got the registry and external extensions to show up.
--I tried find the issue with the attached mockups but not finding yet - i'll see if James can digg it out and share here.
/max
Anyway, food for thoughts.
--
Guillaume--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CALt0%2Bo8ADniRe0tSBnqC0JqDsh7TGKRDwjhF%2Bb_VZp_XOBUwAQ%40mail.gmail.com./max
https://xam.dk/about
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/499A2A68-60D2-4967-9F6D-76858BB5F723%40redhat.com.
Max Rydahl Andersen
> On Mon, Jul 12, 2021 at 12:15 PM Max Rydahl Andersen
> <mand...@redhat.com>
> wrote:
>
>> Hi,
>>
>> I don't really have an idea about how to fix it but I thought maybe
>> just
>> acknowledging the issue collectively could be a good idea and might
>> help to
>> get ideas in shape.
>>
>> When going to https://code.quarkus.io/ , the order of extensions is
>> very
>> confusing:
>>
>>
>> used so it's not a purely alphabetical order
>>
>> unfortunately for some of the extensions is not very natural.
>>
>> Some of the problems I identified:
>>
>>
>> extensions and the first one to mention GraphQL, whereas maybe we
>> would
>> like to push users to SmallRye GraphQL - I noticed that because I was
>> surprised somebody reported an issue with it, I would have expected
>> people
>> to use the SmallRye stuff in priority
>>
>> make smallrye graphql sticky so it shows up sooner ?
>>
>>
>>
>> (typically the JAX-RS Client Reactive extension coming as the 6th
>> one,
>> totally split from the REST Client Reactive one, which should be used
>> in
>> priority)
>>
details.
> We need to set up a meeting with James to see how we could fit
> everything
> together with the new layout.
/max
>> .
>>
>
>
> --
> Andy Damevin