Refactor plone.app.contentrules to provide API methods, which plone.restapi can use

[MrTango]

PLIP (Plone Improvement Proposal)

Responsible Persons

Proposer: @MrTango

Seconder:

Abstract

Currently plone.restapi is directly filling out form data, instead of using Python API methods.
This makes it impossible to decouple plone.app.contentrules UI related code from API code.
We should introduce Python API methods, plone.restapi could use.

Motivation

We want to decouple the UI related code and templates and move it to plone.app.layout, so that headless installations can work without it.

Assumptions

Proposal & Implementation

• Add Python API methods, which plone.restapi/plone.api could use.
• Move UI related code to plone.app.layout and make use of the Python API methods.
• Refacture plone.restapi to use the new Python methods

Deliverables

• Python API methods for all functions in contentrules
• UI Code seperated into plone.app.layout
• updated plone.restapi

Risks

Participants

[MrTango]

@plone/framework-team @plone/classicui-team @plone/restapi-team

[MrTango]

We have to decide if we want to do the effort to separate this or live with the dependency and templates in the headless stack. That's up to debate.

[jensens]

I propose to turn plone.app.contentrules into a core addon, its a perfect candidate.
This should go in an own PLIP right?

[davisagli]

@jensens +1

[mauritsvanrees]

I am +1 for making plone.app.contentrules a core add-on. By extension the same goes for plone.contentrules.

[jensens]

See new PLIP #4119
Overall, making it a core addon does not make this PLIP vanish (except the line "Move UI related.."), plone.restapi would definitely profit from a better API here. Maintainability here would increase too.