v3.24.0

• Comment editing is now available
• Improved auditor logs
• Small UI tuning for edit/delete button locations
• Make sure comments are ordered chronically

v3.23.0

Features:

• Integration to the new Auditor service. All actions are now audited via the new service including unauthorized actions
• It's possible to disable notifications from the config qeta.notifications
• Notification is now sent to also users who have favorited a post

Improvements:

• List operation performance should now be better when using permissions; unnecessary access checks were removed

Bug fixes:

• From and to date filters work also alone; suggestions are now much better in the home page

v3.22.0

Updated to Backstage 1.36.1. To use this release Backstage 1.36.0 or later is required. This is due to a change in the permission integration router, which is moving to use permissionsRegistryService. If you try to run this plugin with an older Backstage version, an error is logged and permissions will be disabled.

Additionally, the deprecated permission condition factories have now been removed from @drodil/backstage-plugin-qeta-backend and moved to @drodil/backstage-plugin-qeta-node

v3.21.0

New features:

• QetaSearchResultListItem is now using the extension. Thanks to @borjapazr for the contribution!
• Entities and tags are now part of URL when filtering questions/answers/collections for easier sharing of specific content

Fixes:

• If permissions are not enabled, conditional authorize does nothing
• Improved handling of 403 Forbidden responses in the frontend

v3.20.3

Answers are filtered correctly based on permissions

v3.20.2

Few performance improvements

v3.20.1

New features

• Possibility to add permission checks for tags and collections
  • IF YOU ARE NOT USING PERMISSIONS: The collections can only be managed by the collection owner and moderators. Separate read and edit access to collections have been removed. Tag creation will work based on the configuration flag qeta.tags.allowCreation and is true by default like previously
  • IF YOU ARE USING PERMISSIONS: Tags cannot be any more updated by anyone. If you want to enable this, add a new permission check, example here. Additionally, you must allow reading tags and collections in your permission policy accoringly.
  • There are a few available rules for each permission, check those out from here
• New QetaSearchResultListItem is exported from @drodil/backstage-plugin-qeta that can be used to show search results in more beautiful way. See https://github.com/drodil/backstage-plugin-qeta/blob/main/docs/search.md for more information
• Q&A home plugin table can now show also articles. In customizable home page this can be selected by the user or this can be passed also as a prop to PostsTableCard component

Improvements

• Permission rules and conditions have been moved to @drodil/backstage-plugin-qeta-node package. The backend package exports these as deprecated and they will be removed in a future release.
• As the loading times can get higher due to permission checks, there are now better loading indicators for each page
• A couple of navigation and rendering improvements all over the UI
• Comments are now stored in one table instead of separate ones for posts and answers. The existing data will be migrated automatically

Fixes

• Search collator can now access the collections and index them properly

v3.20.0

Was not published to npm registry due to TSC issue

v3.19.0

Was not published to npm registry due to TSC issue

v3.18.2

Fixed code blocks going out of screen