pat-select2 depends on an old and customized version of select2. Lets either
update it to the latest version of select2 and get rid of the customizations.
or create a new pattern with the latest version and deprecate the old one.
Motivation
Keep the Classic-UI stack up to date.
Proposal & Implementation
There are two possible implementations:
update pat-select2 to the latest select2 version and document the API changes.
create a new pattern pat-select which uses the latest version of select2 and remove pat-select2 with documentation how to migrate to the new pattern.
Deliverables
I've started upgrading pat-select2 here a while ago (https://github.com/plone/mockup/pull/1295) but depending on the discussion here its maybe better to start off with a new pattern for the new version.
Risks
case 1: updateing pat-select2 -> the select2 API changes radically and addons will not work anymore.
case 2: adding new pattern: addons will also have to migrate their code to the new api
PLIP (Plone Improvement Proposal)
Responsible Persons
Proposer: Peter M. / petschki
Seconder: add your name here
Abstract
pat-select2depends on an old and customized version ofselect2. Lets eitherselect2and get rid of the customizations.Motivation
Keep the Classic-UI stack up to date.
Proposal & Implementation
There are two possible implementations:
pat-select2to the latestselect2version and document the API changes.pat-selectwhich uses the latest version ofselect2and removepat-select2with documentation how to migrate to the new pattern.Deliverables
I've started upgrading
pat-select2here a while ago (https://github.com/plone/mockup/pull/1295) but depending on the discussion here its maybe better to start off with a new pattern for the new version.Risks
case 1: updateing
pat-select2-> theselect2API changes radically and addons will not work anymore. case 2: adding new pattern: addons will also have to migrate their code to the new apiParticipants
@plone/classicui-team