feat(form): add case infos to jexl context

[czosel]

This is convenient when you'd like to write a JEXL expression in a task form attached to some work item, that depends on the case's main documents' form.

Related backend MRs:

• feat(jexl): add main_case_form to info object caluma#2204
• feat(form): add more case info to jexl context caluma#2205

[StephanH90]

Just one question.

[StephanH90]

Don't forget to rename the property once a decision is made but I will approve now.

[StephanH90]

But the naming between the backend and the frontend doesn't match, does it?

In the backend we now have a main_case_form which would be the case.root.form in the frontend, correct?
(https://github.com/projectcaluma/caluma/pull/2204/files#diff-4200093d628340ea25db028f99d1543cb5c63af275a4a670a9c08adee6444effR150-R158)

Should we try to keep the naming consistent between frontend and backend?

[czosel]

But the naming between the backend and the frontend doesn't match, does it?

In the backend we now have a main_case_form which would be the case.root.form in the frontend, correct? (https://github.com/projectcaluma/caluma/pull/2204/files#diff-4200093d628340ea25db028f99d1543cb5c63af275a4a670a9c08adee6444effR150-R158)

Should we try to keep the naming consistent between frontend and backend?

The backend MR was merged a little bit too quickly, here is the follow-up which should line up with the frontend part: projectcaluma/caluma#2205

[czosel]

@anehx I added another test for unlinked documents. Want to take another look?

[anehx]

💯 🚀

[anehx]

🎉 This PR is included in version 12.15.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀