Yes, @ricardo I'm talking about simple static pages describing the components and showing a few links to tools and docs.
"...remember that http status code should be bad request." Thanks @enrique for this point, I will keep a note. On Mon, Aug 12, 2024 at 7:24 PM ricardo zanini fernandes < ricardozan...@gmail.com> wrote: > > You are talking about the 404 page showed if I open > http://localhost:8080/ instead http://localhost:8080/q/dev-ui, am I > right? > > Yes, exactly. During code generation, the serverless workflow or process > component can have a different template for each index.html page, which can > include a brief description of the Apache project, the logo, and a useful > docs link. So, you may have different index pages for each. > > > For the landing page we are talking about something like graphql UI ? > > No, I think what he's trying to say is a very simple static page describing > the component and links to the internal tools, such as GraphQL UI. > > > > On Mon, Aug 12, 2024 at 1:04 PM Enrique Gonzalez Martinez < > elguard...@gmail.com> wrote: > > > For the landing page we are talking about something like graphql UI ? > > UI wont usually be deployed in prod env that is the reason behind the dev > > ui thingy. > > Where is this going to be land runtimes or tooling ? What kind of > > information do you want to show ? If it is just a get method to say > these > > are graphql end points and set just example, as long as it does not > affect > > the graphql behavior i dont think you need a proposal. Just modify the > > handlers, but remember that http status code should be bad request. > > > > El lun, 12 ago 2024, 18:09, Fabrizio Antonangeli < > fantonang...@apache.org> > > escribió: > > > > > You are talking about the 404 page showed if I open > > > http://localhost:8080/ instead http://localhost:8080/q/dev-ui, am I > > > right? > > > I confirm we have a 404 in this case. > > > > > > Sure I can work on it. In this case the information to show is even > > > more generic... We need to think what to show in this page. > > > > > > On Mon, 2024-08-12 at 11:47 -0400, ricardo zanini fernandes wrote: > > > > +1! > > > > > > > > This will greatly enhance the user experience with those services. > > > > Additionally, we have the same problem with SonataFlow and jBPM. > > > > IIRC, we > > > > have 404 pages on services generated with Kogito at the root path. > > > > > > > > Can you send/work on a proposal for those too? > > > > > > > > Cheers! > > > > > > > > On Mon, Aug 12, 2024 at 11:43 AM Fabrizio Antonangeli < > > > > fantonang...@apache.org> wrote: > > > > > > > > > Hi Jason, > > > > > It will not be a new Dev UI screen. It should be a simple html page > > > > > as > > > > > a first step which will be available at the url of the service, if > > > > > the > > > > > user tries to open it with the browser > > > > > (eg. http://localhost:8080/graphql) and will be integrated within > > > > > the > > > > > service image. > > > > > > > > > > On Mon, 2024-08-12 at 15:01 +0000, Jason Porter wrote: > > > > > > When you say "landing page" are you talking about a new dev ui > > > > > > screen? A new section/page on our web site? Something else? I'm > > > > > > not > > > > > > understanding the full proposal. > > > > > > > > > > > > On 2024/08/12 10:56:44 Fabrizio Antonangeli wrote: > > > > > > > Hello everyone, > > > > > > > > > > > > > > I am proposing we create two new landing pages, which could > > > > > > > optionally > > > > > > > evolve into web applications in the future, for the Data Index > > > > > > > and > > > > > > > the Job > > > > > > > Service. This initiative aims to replace the "Query is missing" > > > > > > > page error > > > > > > > that currently appears when users access the URL > > > > > > > http://localhost:4000/graphql and provide the user with some > > > > > > > information. > > > > > > > Since these two services are consumed by BPMN and SonataFlow, > > > > > > > the > > > > > > > landing > > > > > > > pages should not contain specific references to them. Instead, > > > > > > > they > > > > > > > should > > > > > > > include a brief generic introduction and point to the general > > > > > > > GraphQL > > > > > > > documentation (https://graphql.org/learn/) for the Data Index. > > > > > > > Considering the architecture, we can integrate these landing > > > > > > > pages > > > > > > > within > > > > > > > the kie-tools repository, to allow the reuse of components, and > > > > > > > incorporate > > > > > > > them into the DI/JS images. > > > > > > > > > > > > > > If this proposal is accepted, I am also available to work on a > > > > > > > graphical > > > > > > > mockup to be shared here for feedback. > > > > > > > > > > > > > > Regards, > > > > > > > Fabrizio Antonangeli > > > > > > > > > > > > > > > > > > > ----------------------------------------------------------------- > > > > > > ---- > > > > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > > > > > > For additional commands, e-mail: dev-h...@kie.apache.org > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------- > > > > > -- > > > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > > > > > For additional commands, e-mail: dev-h...@kie.apache.org > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@kie.apache.org > > > For additional commands, e-mail: dev-h...@kie.apache.org > > > > > > > > >
