@dextinity/cms-admin@10.4.0
Minor Changes
-
4b9ead5: Add
iconoption toTipTapInlineStyleCustom inline styles shown in the rich text toolbar's "More options" menu can now specify an
icon, displayed next to the label the same way Superscript/Subscript already are:createTipTapRichTextBlock({ inlineStyles: [ { name: "highlight", label: <FormattedMessage id="..." defaultMessage="Highlight" />, icon: RteHighlight, element: (props) => <span style={{ backgroundColor: "#fff3cd" }} {...props} />, }, ], });
iconis optional; menu items without one keep rendering as before. -
4b9ead5: Move custom TipTap inline styles into the toolbar's "More options" menu
Custom
inlineStyles(e.g. a project-specific "Uppercase" style) used to render as their own always-visible dropdown in the rich text toolbar. They now appear as toggleable menu items inside the "More options" ("...") menu, next to Superscript/Subscript, matching how the previous Draft.js-based rich text editor exposed custom inline styles as toolbar toggles rather than a separate dropdown. -
a00f0b2: Support wildcard values for content scope dimensions in
getContentScopesForUsergetContentScopesForUsercan now use the wildcard value"*"as the value of a content scope dimension to grant access to any value for that dimension. The wildcard is matched during the content scope check, so it does not need to be part ofavailableContentScopes.Example
getContentScopesForUser(user: User): ContentScopesForUser { // Grant access to every language within the "main" domain return [{ domain: "main", language: "*" }]; }
For users with access to all content scopes,
currentUser.permissions[].contentScopesnow returns a single wildcard scope (e.g.[{ domain: "*", language: "*" }]) instead of the enumeratedavailableContentScopes. The defaultisAllowedandcurrentUser.allowedContentScopeshandle the wildcard; a customisAllowedmust treat"*"as matching any value of a dimension.
Patch Changes
-
b6cbbd9: Move icons to the start of the TipTap "More options" menu items
Superscript, Subscript, and custom inline-style menu items placed their icon directly after the label using a custom flexbox layout, so the icon's horizontal position varied with the label's length. They now use MUI's
ListItemIcon/ListItemTextwith the icon leading the label, matching MUI's own menu item convention.
@dextinity/cms-api@10.4.0
Minor Changes
-
a00f0b2: Support wildcard values for content scope dimensions in
getContentScopesForUsergetContentScopesForUsercan now use the wildcard value"*"as the value of a content scope dimension to grant access to any value for that dimension. The wildcard is matched during the content scope check, so it does not need to be part ofavailableContentScopes.Example
getContentScopesForUser(user: User): ContentScopesForUser { // Grant access to every language within the "main" domain return [{ domain: "main", language: "*" }]; }
For users with access to all content scopes,
currentUser.permissions[].contentScopesnow returns a single wildcard scope (e.g.[{ domain: "*", language: "*" }]) instead of the enumeratedavailableContentScopes. The defaultisAllowedandcurrentUser.allowedContentScopeshandle the wildcard; a customisAllowedmust treat"*"as matching any value of a dimension.
@dextinity/mail-react@10.4.0
Patch Changes
-
98c1097: Fix head CSS lost after the first
@mediablock in Outlook.com and the Outlook apps for iOS and AndroidThese clients stop reading a
<style>tag at the first}}, which minified CSS writes at the end of every@mediablock. -
bb5d22a: Apply the Storybook addon's "Use public image URLs" toggle to the Outlook VML image source
-
583dd13: Fix
borderRadiuson images in classic Outlook, which rounded corners twice as much as the value asked for
@dextinity/site-react@10.4.0
Patch Changes
- 0e88bab: Fix block preview outlines being cut off when
IFrameBridgeProviderdoes not start at the left edge of the page, for instance because of padding or centering