Feature: Checklist

[pmattmann]

• Merge this PR
• Frontend:
  • Administration: Manage checklists
  • ChecklistNode

I would merge the backend early so that the two frontend components can be developed at the same time.

Relates to #4936

[manuelmeister]

Currently while prototyping the frontend (#5460), I thought to myself if we probably need an (optional) numbering system for the checklist items, similar to the schedule entries? What do you think?

While trying to recreate the PBS checklist, I realized that 64 characters are not enough for checklist item texts, or then we need an additional description for longer texts.

[pmattmann]

Currently while prototyping the frontend (#5460), I thought to myself if we probably need an (optional) numbering system for the checklist items, similar to the schedule entries? What do you think?

Currently this is not a requirement.
Shouldn't this question be discussed here #4936?
We will no longer consider the PR after the merge.

While trying to recreate the PBS checklist, I realized that 64 characters are not enough for checklist item texts, or then we need an additional description for longer texts.

I am happy to adapt this. How many characters should be supported?

[BacLuc]

Very cool, thank you.
Some technicalities, most of which we could tackle later

[pmattmann]

Maybe if you had a transient field, api platform woud fetch the Items directly for you?

@BacLuc
Do you have any idea how to do this?

[BacLuc]

Maybe if you had a transient field, api platform woud fetch the Items directly for you?

@BacLuc Do you have any idea how to do this?

don't wait for this.
I just remembered that api platform uses the doctrine annotations to find out, what the related entitiy is.
Without that, it is difficult to find the relation. We can still change it later.

[github-actions]

⛔ Feature branch deployment currently inactive.

If the PR is still open, you can add the deploy! label to this PR to trigger a feature branch deployment.

[BacLuc]

Thank you very much