Moved thumbnailService and Helper Classes to cap-base-models

This note covers changes to private API. Although private API is not subject to release notes and it can be changed without further notice we detected that this API was leaked in the blueprint so the code might have been copied or customized that is why we declared this change as possibly breaking.

Follow Section, “Moved thumbnailService and Helper Classes to cap-base-models” for upgrade information.

(CMS-22223)

Third-Party Update: rxjs from 6.x to 7.x

We now use the latest major version of rxjs in the studio-client workspace. In case you made any use of it in one of your packages make sure to upgrade rxjs as well. The changes can be seen here: https://rxjs.dev/deprecations/breaking-changes

(CMS-22220)

Added Support for Multiple Bookmarks

Inside the library, multiple content items can be bookmarked now. Additional properties have been added to Editor_properties.ts for this:

  Bookmark_button_add_multi_text: "Add Bookmarks",
  Bookmark_button_add_multi_tooltip: "Bookmark the selected content items",
  Bookmark_button_remove_multi_tooltip: "Remove bookmarks",
  Bookmark_button_remove_multi_text: "Remove Bookmarks",

(CMS-21454)

Studio Client Unified API: Improved TypeScript Types

The part of Studio Client API that corresponds to CMCC's Unified API in Java (content, workflow, users) has been overhauled to provide more precise TypeScript types. Studio Client TypeScript code has been migrated from ActionScript, where it was not possible to describe callback function signatures and certain complex types (unions, intersections, generic types / type parameters). With TypeScript, now it is. To provide an improved formal description of the API, all vague types like AnyFunction or any have been replaced by more specific types, mostly already given in the textual documentation. This affects the packages @coremedia/studio-client.client-core and @coremedia/studio-client.cap-rest-client. Formally, changing the API to be more specific is a breaking change. But the required callback signatures, array element types and union types have already been documented as text, so if your code adheres these constraints, it is not going to break. Otherwise, only the TypeScript types of your code might have to be adapted, or the new, more precise types may even find hidden bugs in client code that need to be fixed.

(CMS-21089)

Fixed babel Configuration in studio-client

We fixed our internal babel configuration for the studio-client so code is no longer transpiled using the so called "loose" mode. This will cause that the resulting JavaScript code is now more precise regarding ES6 standards than before.

Follow Section, “Fixed babel Configuration in studio-client” for upgrade information.

(CMS-21144)