Peter Mathis

for me, in python 3.7 the code-analysis problem is gone ... allthough 3.6 still failing ... see https://travis-ci.org/plone/plone.app.blocks/builds/490072439

Thanks for the hint with `.delegate()` ... me never used that either ... I'll request a pull later today.

See my comment here https://community.plone.org/t/disabled-widgets-mode-plone-6-classic/18090/12 This is an issue in current `p.a.z3cform==4.3.x` for certain widgets but fixed in `4.4.x`

I've also removed this part: https://github.com/plone/documentation/pull/1571/files#diff-2a092039aef3cb61f8a3fdc888afaaca68f5dd8a64b6b612cbf3c3d2af1b01d4L591-L603 `plone.directives.form` is outdated and the default value hint is already covered here https://github.com/plone/documentation/pull/1571/files#diff-2a092039aef3cb61f8a3fdc888afaaca68f5dd8a64b6b612cbf3c3d2af1b01d4L591-L603

Sorry for the confusion. I've only de-duplicated the "default value hint" in `schemas.md` and remove the old link to `plone.directives.form` ... the hint is already in the warning box here...

just had a related issue with the CSV export in latest 1.7-maintenance Plone 4.3 setup. Excel still does not convert to utf8 encoding correctly when opening the downloaded CSV directly...

Sorry, its not about ``s its about the CSS class `.list-group-numbered` which cannot have a offset right now. As long as its documented I'm ok with it.

see https://codepen.io/petschki/pen/MWXgjBx

Sorry, I never had this one. But undertemplate looks good as we might get rid of `underscore` completely then, because it's mainly used for templates since ES6 rewriting.

While migrating `pat-select2` (unfinished #1295 🫣) we talked about replacing relateditems with a new pattern not using select2 anymore. @MrTango had an insteresting approach which we maybe should look more...