In JS and CSS and Jelly we have no concepts of encapsulation and APIs in the moment. Everything what is available in the browser is public by default. In JS this is even more complex to hide than in Java.
I think that users also will benefit from views that do not load the same library multiple times (loading time of a page). Also it duplicates the development effort if we create a plugin API for each JS library that we are using in core. > Am 22.05.2023 um 22:58 schrieb Basil Crow <m...@basilcrow.com>: > > https://github.com/jenkinsci/bootstrap5-api-plugin/pull/213 (comment) > concerns me: > >> Popper2 is now part of Jenkins core. > > As far as I can tell the Popper dependency was added when replacing > YUI tooltips with Tippy in > https://github.com/jenkinsci/jenkins/pull/6408. Has this abstraction > now leaked as an implementation detail that plugins are starting to > depend on? > > Any recent JavaScript dependencies of Jenkins core like Tippy and > Popper should be built and packaged in such a way that they are not > exposed to plugins. Plugins that want to use Popper should be using > the Popper plugin. Both should be able to coexist at the same time. > Ignoring this separation of concerns leads to maintenance problems in > the future. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpLEVif3Es6yJafE29zkW6gxSROTLH0dV-cJ5sBrr5Gzw%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3FE63006-128C-44CE-8DD5-E6BD2C9ADDE4%40gmail.com.
