Fixed Regression in HeadlessServer: REST calls pass through error messages via JSLT transformed responses

Starting with 2404 (the introduction of Spring-GraphQL-Library), GraphQL responses of JSLT transformed persisted queries did not pass through potential GraphQL error messages.

This regression was fixed. In order not to break the current version, the fix must be enabled by an additional compatibility flag caas.rest.error-messages-over-jslt-enabled=true|false. To stay non-breaking within versions 2406 and 2412, the flag defaults to false!

If the flag is activated, all JSLT templates must be updated, as the JSON path of the response now includes the explicit “data” property again and the potential “errors” property of course. In effect this means, the former JSLT templates of version 2310-LTS and prior will work again.

(CMS-27699)

HeadlessServer now also supports type conversion of path segments used as GraphQL input variables

Previously, HeadlessServer converted HTTP request parameters into the necessary type for a GraphQL input variables only. With this fix type conversion is now also supported for path segments of the HTTP request path.

(CMS-27635)

Bugfix HeadlessServer: Multiple inheritance for GraphQL types overwrites fetch expression by last type

HeadlessServer overwrote the fetch expression when a GraphQL type used the @inherit directive with two or more types, which also implemented GraphQL interfaces. The problem was fixed.

(CMS-27168)

Bugfix: Missing validation of invalid, embedded content in richtext in HeadlessServer

Richtext transformation did not filter invalid, embedded content links. The problem was fixed invoking the filter predicates during richtext transformation.

The changes made new constructors in the public API necessary. For backward compatibility, the former constructors were kept in the code as legacy constructors but marked deprecated for removal. It is highly recommended not to use the deprecated constructor anymore and instead update existing custom code to use the new constructors. Also be aware, using the old constructors will work but will also keep the old, wrong behavior!

(CMS-26978)