Open laulaz opened 3 years ago
@thet @jensens any advice on this ? 😉
Same here ... so the solution would be to lift patternslib version here to the latest patterns release right? https://github.com/Patternslib/Patterns/releases ... there, the parser ist fixed ... among many other possibly breaking changes ... maybe then we have to bump plone.patternslib version to 2.0.0 for Plone 6 ...
/cc @thet do you have any advice on this? is it possible to get patternslib 4.0.0 into plone.patternslib 2.0.0 ?
with patternslib 7.X, I'm quite confused on how it will work on plone 6. We have:
Patternslib -> plone.patternslib -> pat-leaflet.
With es6 and module federation, how this will work?
IIUC in Plone6 we do not need plone.patternslib
anymore, because its included in mockup. But https://github.com/Patternslib/pat-leaflet needs some love to work with Plone 6 ES6 updates ...
So mockup will include (via npm?) Patternslib, which must be updated (at least for plone.patternslib
) to work with es6. Is there a way I can test this setup, is the es6 plip enough?
mockup#es6 includes patternslib here https://github.com/plone/mockup/blob/es6/package.json#L10 ... I think this could savely be updated to 7.0.1 there ... so plone.patternslib is obsolete for mockup#es6 and therefore Plone 6 ... but as said, I don't think pat-leaflet
is working right now with patternslib>=6.4.0 ... @thet am I right?
@yurj you could simply add https://github.com/Patternslib/pat-leaflet to your sources/auto-checkout along with the plip-3411 checkouts and see what happens 💣
The new 2.1.5 has the same problem.
On Plone 6 (buildout.coredev), we have a traceback when trying to use leaflet (because of
andSelf
removal in jQuery > 3):Replacing it by
addBack()
works like a charm ... for this pattern.I don't know how jQuery versions are handled between the different Plone packages / patterns, so I would like to have inputs on the best way to fix that everywhere without breaking code still using old jQuery version(s).