apostrophe - npm Package Versions

3.47.0 (2023-05-05)

Changes

• Since Node 14 and MongoDB 4.2 have reached their own end-of-support dates, we are no longer supporting them for A3. Note that our dependency on jsdom 22 is incompatible with Node 14. Node 16 and Node 18 are both still supported. However, because Node 16 reaches its end-of-life date quite soon (September), testing and upgrading directly to Node 18 is strongly recommended.
• Updated sluggo to version 1.0.0.
• Updated jsdom to version 22.0.0 to address an installation warning about the word-wrap module.

Fixes

• Fix extendQueries to use super pattern for every function in builders and methods (and override properties that are not functions).

3.46.0 (2023-05-03)

Fixes

• Adding or editing a piece no longer immediately refreshes the main content area if a widget editor is open. This prevents interruption of the widget editing process when working with the @apostrophecms/ai-helper module, and also helps in other situations.
• Check that e.doc exists when handling content-changed event.
• Require updated uploadfs version with no dependency warnings.

Adds

• Allow sub-schema fields (array and object) to follow parent schema fields using the newly introduced following: '<parentField' syntax, where the starting < indicates the parent level. For example <parentField follows a field in the parent level, <<grandParentField follows a field in the grandparent level, etc. The change is fully backward compatible with the current syntax for following fields from the same schema level.

Changes

• Debounce search to prevent calling search on every key stroke in the manager modal.
• Various size and spacing adjustments in the expanded Add Content modal UI

3.45.1 (2023-04-28)

Fixes

• Added missing styles to ensure consistent presentation of the rich text insert menu.
• Fixed a bug in which clicking on an image in the media manager would close the "insert image" dialog box.
• Update html-to-text package to the latest major version.

3.45.0 (2023-04-27)

Adds

• Rich text widgets now support the insert option, an array which currently may contain the strings image and table in order to add a convenient "insert menu" that pops up when the slash key is pressed. This provides a better user experience for rich text features that shouldn't require that the user select existing text before using them.
• Auto expand inline array width if needed using width: max-content in the admin UI.
• The "browse" button is now available when selecting pages and pieces to link to in the rich text editor.
• The "browse" button is also available when selecting inline images in the rich text editor.
• Images are now previewed in the relationship field's compact list view.
• The new apos-refreshing Apostrophe bus event can be used to prevent Apostrophe from refreshing the main content zone of the page when images and pieces are edited, by clearing the refresh property of the object passed to the event.
• To facilitate custom click handlers, an apos.modal.onTopOf(el1, el2) function is now available to check whether an element is considered to be "on top of" another element in the modal stack.

Changes

• The v-click-outside-element Vue directive now understands that modals "on top of" an element should be considered to be "inside" the element, e.g. clicks on them shouldn't close the link dialog etc.

Fixes

• Fix various issues on conditional fields that were occurring when adding new widgets with default values or selecting a falsy value in a field that has a conditional field relying on it. Populate new or existing doc instances with default values and add an empty null choice to select fields that do not have a default value (required or not) and to the ones configured with dynamic choices.
• Rich text widgets save more reliably when many actions are taken quickly just before save.
• Fix an issue in the oembed field where the value was kept in memory after cancelling the widget editor, which resulted in saving the value if the widget was nested and the parent widget was saved. Also improve the oembed field UX by setting the input as readonly rather than disabled when fetching the video metadata, in order to avoid losing its focus when typing.

3.44.0 (2023-04-13)

Adds

• checkboxes fields now support a new style: 'combobox' option for a better multiple-select experience when there are many choices.
• If the new guestApiAccess option is set to true for a piece type or for @apostrophecms/page, Apostrophe will allow all logged-in users to access the GET-method REST APIs of that module, not just users with editing privileges, even if publicApiProjection is not set. This is useful when the goal is to allow REST API access to "guest" users who have project-specific reasons to fetch access content via REST APIs.
• test-lib/utils.js has new createUser and loginAs methods for the convenience of those writing mocha tests of Apostrophe modules.
• batchOperations permissions: if a permission property is added to any entry in the batchOperations cascade of a piece-type module, this permission will be checked for every user. See batchOperations configuration in modules/@apostrophecms/piece-type/index.js. The check function checkBatchOperationsPermissions can be extended. Please note that this permission is checked only to determine whether to offer the operation.

Fixes

• Fix child page slug when title is deleted

3.43.0 (2023-03-29)

Adds

• Add the possibility to override the default "Add Item" button label by setting the itemLabel option of an array field.
• Adds touch task for every piece type. This task invokes update on each piece, which will execute all of the same event handlers that normally execute when a piece of that type is updated. Example usage: node app article:touch.

Fixes

• Hide the suggestion help from the relationship input list when the user starts typing a search term.
• Hide the suggestion hint from the relationship input list when the user starts typing a search term except when there are no matches to display.
• Disable context menu for related items when their relationship field has no sub-fields configured.
• Logic for checking whether we are running a unit test of an external module under mocha now uses includes for a simpler, safer test that should be more cross-platform.

3.42.0 (2023-03-16)

Adds

• You can now set style: table on inline arrays. It will display the array as a regular HTML table instead of an accordion. See the array field documentation for more information.
• You can now set draggable: false on inline arrays. It will disable the drag and drop feature. Useful when the order is not significant. See the array field documentation for more information.
• You can now set the label and icon to display on inline arrays when they are empty. See the array field documentation for more information.
• We have added a new and improved suggestion UI to relationship fields.
• The utilityOperations feature of piece types now supports additional properties: relationship: true (show the operation only when editing a relationship), relationship: false (never show the operation when editing a relationship), button: true, icon and iconOnly: true. When button: true is specified, the operation appears as a standalone button rather than being tucked away in the "more" menu.
• In addition, utilityOperations can now specify eventOptions with an event subproperty instead of modalOptions. This is useful with the new edit event (see below).
• Those extending our admin UI on the front end can now open a modal to create or edit a page or piece by calling await apos.doc.edit({ type: 'article' }) (the type here is an example). To edit an existing document add an _id property. To copy an existing document (like our "duplicate" feature) add a copyOf property. When creating new pages, type can be sent to @apostrophecms/page for convenience (note that the type property does not override the default or current page type in the editor).
• The edit Apostrophe event is now available and takes an object with the same properties as above. This is useful when configuring utilityOperations.
• The content-changed Apostrophe event can now be emitted with a select: true property. If a document manager for the relevant content type is open, it will attempt to add the document to the current selection. Currently this works best with newly inserted documents.
• Localized strings in the admin UI can now use $t(key) to localize a string inside an interpolated variable. This was accomplished by setting skipOnVariables to false for i18next, solely on the front end for admin UI purposes.
• The syntax of the method defined for dynamic choices now accepts a module prefix to get the method from, and the () suffix. This has been done for consistency with the external conditions syntax shipped in the previous release. See the documentation for more information.
• Added the viewPermission property of schema fields, and renamed permission to editPermission (with backwards compatibility) for clarity. You can now decide if a schema field requires permissions to be visible or editable. See the documentation for more information.
• Display the right environment label on login page. By default, based on NODE_ENV, overriden by environmentLabel option in @apostrophecms/login module. The environment variable APOS_ENV_LABEL will override this. Note that NODE_ENV should generally only be set to development (the default) or production as many Node.js modules opt into optimizations suitable for all deployed environments when it is set to production. This is why we offer the separate APOS_ENV_LABEL variable.

Fixes

• Do not log unnecessary "required" errors for hidden fields.
• Fixed a bug that prevented "Text Align" from working properly in the rich text editor in certain cases.
• Fix typo in @apostrophecms/doc-type and @apostrophecms/submitted-drafts where we were using canCreate instead of showCreate to display the Create New button or showing the Copy button in Manager modals.
• Send external condition results in an object so that numbers are supported as returned values.

3.41.1 (2023-03-07)

No changes. Publishing to make sure 3.x is tagged latest in npm, rather than 2.x.