When was 5.2 released

Close Menu Docs. Developer Guides. Code Reference. Code of Conduct. Productivity Tools. Community Forum. What We Support. This is the third minor release of and has commits from 27 contributors in WooCommerce core. WooCommerce Blocks 4. Please take a look at the release posts for 4. WooCommerce Admin 2. This new package contains lots of bug fixes and stability improvements. Changes also for the intermediate versions up to 2.

The option is enabled by default. So what is new in 5. Updated Extensions Domain Manager plugin now places domain names in their own client and client profile widget.

Domain Manager plugin now automatically uses the default welcome email when adding a new TLD. Domain Manager plugin now allows pricing to be set under Configuration for options like Email Forwarding. Domain Manager plugin now asks for input when changing a TLDs registrar module only when necessary. Order plugin update when using multi-currency, a currency selector now appears on domain order pages.

Order plugin update to add a TLD pricing table below the domain search box on order pages. Plesk module now allows an account limit and new add order option to be set. Added an option so that staff and clients can renew services and domains in advance. Packages have been split into different tabbed sections for simplicity and organization.

Updated the client area to add a contact list box to the left column of the dashboard. These breadcrumbs allow the compiler to produce precise diagnostics, often with actionable fixes, that lead the developer toward correct code. Below are a few examples of improved error messages.

The Swift 5. You can find out more about the new diagnostic architecture on a previously published blog post dedicated to that topic. Faster completion by eliminating unnecessary type checking. For large files it can speed-up code completion by 1. Now can supply names of implicit members for incomplete dictionary literals and incomplete ternary expressions:.

Easier to read types when they appear in the results. Using opaque result types e. Stopped printing parent types if not necessary. For example, in Swift 5. The two modes have tradeoffs in compilation speed and amount of code optimization performed. Incremental builds are great during development where not every file in the project needs to be recompiled, and maximum optimization is not critical. Whole Module Optimization gives the compiler a more complete view of the entire code base and therefore a greater ability to optimize.

In an Incremental mode build, the work of rebuilding a module is split among multiple compilation tasks that run in parallel. For every source file that is rebuilt, there is exactly one associated compilation task responsible for type checking and generating code for the declarations in that source file. Since Swift declarations such as functions, properties, types, etc.

This cross-file referencing of declarations can decrease efficiency of an Incremental mode build because it can duplicate type-checking work across compilation tasks. In contrast, Whole Module compilation works by processing all the code in a module in one compilation task.

While there is no duplication of type checking work across compilation tasks, there is no parallelism when compiling the code in a module. Whole Module compilation, however, gives the compiler more visibility in one go over the code in a module and thus enables more code optimizations.

The build time advantage of Incremental over Whole Module compilation diminishes with the amount of duplicated work each compilation task performs.