Releases: VirtusLab-Open-Source/strapi-plugin-comments
Releases · VirtusLab-Open-Source/strapi-plugin-comments
v2.0.0 - Public Beta #2
Fixes
- fix default GET operation for client Public API
v2.0.0 - Public Beta #1
❗ ❗ This is a first beta release of a plugin for Strapi v4. Do not use it on production ❗ ❗
After a while of development we're delighted to present you the first beta release of Comments Plugin which is complete re-write for v4.
Already delivered:
- Listing comments
- Discussion discovery
- Abuse reports flow
- Public API
To be done:
- Advanced filtering by relations and statuses
- GraphQL support
- Database migrations for v3 -> v4
- Updates page - which is going to serve the most recent events happen
- Reports page - which is going to be dedicated for a special new role which might only review the reports
- Settings page - which will allow to change settings on the UI rather than via config file
v1.0.4
v1.0.2
v1.0.2 - Public Beta #1
Features
- GQL support provided #54
v1.0.1
v1.0.1 - Public Beta #7
Features
- filtering panel introduced for comments
- possibility to filter by relation type and exact entity
- support for filters query parameters
Fixes
- multiple mongoDB compat issues fixes
threadOf
property fix #40
v1.0.1 - Public Beta #6
Fixes
- Based on comment in #25, filters & query are now applied only to the root level of comments.
v1.0.1-beta.4
Feature
- introduce query parameters support ( #25 #29 )
- introduce email validation for non-strapi users ( #29 )
Fixes
- fix the 500 error while fetching comments in version
v1.0.1-beta.3
Migration
Those developers who has been overwriting / extending the logic a service methods need to migrate their usage of:
await strapi.plugins.comments.services.comments.findAllInHierarchy(relation, null, true)
to
await strapi.plugins.comments.services.comments.findAllInHierarchy(relation, query, null, true)
because of introduced support for query parameters
v1.0.1 - Public Beta #3
Features
- support for bad word filtering customization in the config file