The parameter validation decorators should be reworked.

[jaroel]

Parameter validation is currently handled by function decorators. This has the following downsides:
A. Required parameters are defined with '=None'.
This is really non-pythonic and unhelpful to IDEs and (more) experienced programmers.
Required arguments should never have a default value.

B. Debugging the function calls is more-or-less impossible.
If you try to PDB into an plone.api function, the only thing you'll see is '(1)create()'. This is the same problem we have with TTW python scripts.

There's also the overhead of function calls, but that's clearly moot when you're creating content, or doing a workflow transition.

[jaroel]

Point A is easily fixed by remove the '=None' for required parameters.
Point B can be resolved by moving the decorators' functionality inside the functions.

[pbauer]

👍 for removing the decorators. They are nice when programming plone.api but really annoying when using and debugging it.

[ale-rt]

Yes, decorators should be removed.
Anyway to not change things too much for the moment I updated in #606 the required_parameters decoractor to also support arguments that do not have a default value.

[davisagli]

Based on https://github.com/plone/plone.api/blob/main/docs/about.md#prefer-keyword-arguments, there was a design decision to require keyword arguments, so that the names are always specified by the caller and there is flexibility to change the order of the arguments.

These days there is a better way to enforce this in Python. https://peps.python.org/pep-3102/ -- I think we should switch to specifying keyword-only arguments this way. Then it's possible to have keyword-only arguments with no default (i.e. ones that are required) without needing a decorator to enforce it.

Hmm, that's probably too big a backwards-incompatible change though, because so far it was not actually required to use keyword arguments, but only recommended.