Home

>

Tools

>

Strapi

>

Releases

>

3.0.0-beta.18.6

Strapi Release: 3.0.0-beta.18.6

Tag Name: v3.0.0-beta.18.6

Release Date: 1/23/2020

Strapi LogoStrapi

Open-source headless CMS built with Node.js. Provides developers with complete freedom in choosing their favorite tools and frameworks for frontend development.

TL;DR

Strapi v3.0.0-beta.18.6 focuses on fixing a critical bug in the MongoDB dynamic zone delete query, while also introducing significant improvements to the front-end testing infrastructure and ESLint configuration. This release enhances code quality and stability, particularly for MongoDB users working with dynamic zones.

Highlight of the Release

    • Fixed critical bug in MongoDB dynamic zone delete query
    • Added extensive test coverage for Content-Type Builder reducer and actions
    • Improved ESLint configuration for front-end files
    • Enhanced UI with scrollbar fix for webhooks left menu

Migration Guide

No migration steps are required for this release. This is a bug fix release that can be safely upgraded to without any special considerations.

Upgrade Recommendations

This upgrade is highly recommended for MongoDB users working with dynamic zones due to the critical bug fix for delete operations. The fix ensures proper data management when deleting dynamic zone content.

For all other users, this upgrade is recommended but not critical, as it primarily includes testing improvements and ESLint configuration enhancements that benefit developers working on the Strapi codebase.

Bug Fixes

Critical Fixes

  • Fixed a critical issue with MongoDB dynamic zone delete queries (#5058)
    • Resolved problems when deleting dynamic zone content in MongoDB databases
    • Ensures proper data cleanup when removing dynamic zone elements

UI Fixes

  • Fixed timestamp display issues (#5040)
  • Added scrollbar to webhooks left menu for better navigation (#5042)

New Features

Testing Infrastructure Improvements

  • Added comprehensive test coverage for Content-Type Builder front-end functionality
  • Implemented tests for reducer basics, simple actions, and complex operations
  • Added specific tests for:
    • Adding common attributes to content types
    • Adding components and dynamic zones
    • Creating and managing relations between content types
    • Removing fields from content types
    • FormModal reducer functionality

Developer Experience Enhancements

  • Improved ESLint configuration for front-end files
  • Added new ESLint rules for better code consistency:
    • newline-before-return rule
    • New line before if statements
  • Enhanced makeUnique utility function

Security Updates

No security fixes were mentioned in this release.

Performance Improvements

No specific performance improvements were highlighted in this release. The focus was primarily on bug fixes, testing infrastructure, and developer experience enhancements.

Impact Summary

This release addresses a critical bug affecting MongoDB users working with dynamic zones, ensuring proper data deletion operations. While this is the primary user-facing change, the release also includes substantial improvements to the development infrastructure with extensive test coverage for the Content-Type Builder and enhanced ESLint configurations.

The MongoDB fix is particularly important as it resolves potential data integrity issues when working with dynamic zones. Without this fix, users might experience incomplete data deletion or orphaned records when removing dynamic zone content.

The testing improvements, while not directly visible to end users, significantly enhance the stability and reliability of the Content-Type Builder functionality, which is a core component of Strapi. The ESLint configuration improvements help maintain code quality and consistency across the codebase.

Full Release Notes

Statistics:

File Changed238
Line Additions5,817
Line Deletions922
Line Changes6,739
Total Commits51

User Affected:

  • Fixed critical issue with dynamic zone deletion queries that was affecting MongoDB users
  • More reliable data management when working with dynamic zones

Contributors:

soupettevirginiekyalexandrebodin