That would be very helpful if we would have a more modular layout. So
individual pages can use individual libraries without loosing the other core
definitions. One problem I see here is that the breadcrumbs, footer, header,
etc. already use some of these old libraries. If we do not load them
> On 28. May 2019, at 17:53, Matt Sicker wrote:
>
> parallel set of layout tags
We could also parameterize the regular l:layout. We already do something
similar for columns.
l:html was quickly deprecated and integrated into l:layout.
(Or perhaps we could move inclusion of libraries as an
Almost sounds like it'd be a good idea to start a parallel set of
layout tags that don't bundle outdated JS libraries. That would be a
larger effort, but it might make it easier to make the UI nicer.
On Sun, May 26, 2019 at 4:36 PM 'Gavin Mogan' via Jenkins Developers
wrote:
>
> Okay, if I
Okay, if I continue to move forward with this plugin, maybe i'll make a PR
that allows you to skip loading the libraries (an attribute for the layout
tag). For now, for the POC, skipping layout is fine.
On Sun, May 26, 2019 at 1:33 PM Ullrich Hafner
wrote:
> I don’t think that this is feasible.
I don’t think that this is feasible. While prototype (especially the totally
ancient version we are using) is breaking a lot of modern JS libs (chartJS,
jQuery, BS, etc.) it is somewhat coupled with almost every UI thing in Jenkins.
I tried to update it to the latest version, but needed to
I'm slowly working on my proof of concept graphql server for jenkins but
ran into trouble including the development console.
As per https://github.com/prisma/graphql-playground/issues/1008 it looks
like prototype and graphql are not playing nice.
Is there a way to get the full layout
