What's New (Page 7 of 9)
The files and tests sections of your Wallaby configuration now support an extra property, hideFromErrorStackTrace. The hideFromErrorStackTrace setting is a boolean property that defaults to false; if set to true, Wallaby will exclude the file from error stack traces.
By default, Wallaby’s Time Travel Debugger limits the number of available debug steps to ensure that your computer’s performance (memory and CPU load) is not adversely affected. The default value of 1,000,000 steps may now be changed using the maxTraceSteps setting.
For VS Code, Wallaby’s Output Inspector now provides settings to control when the Output Inspector will be automatically displayed. To adjust your settings, use the Automatic Display and Automatic Display Debugger Override VS Code Wallaby settings.
If for some reason you are logging stack traces within console.log messages and you would like the stack traces to be mapped back to your original source code then you may use the mapConsoleMessagesStackTrace setting.
Previously only VS Code and JetBrains editors supported Wallaby’s Update Snapshot commands. These commands now exist for all editors.
In addition to adding these commands, the Run Line Tests, Run File Tests and Run Project Tests commands no longer update snapshots;
instead, use the Update Test Snapshots, Update File Snapshots and Update Project Snapshots commands.
For VS Code, Wallaby’s new Output Inspector provides an ergonomic and convenient way of inspecting logged values and errors details in a rich editor-friendly manner. Information is displayed in a code editor window, providing rich keyboard support and allowing you to stay in your coding mindset so that you don’t lose your flow. This feature is also coming soon for JetBrains editors.
Wallaby now has first class support for Yarn 2. If you use Yarn 2 and want to use Wallaby, then check out the Yarn 2 section of our docs.
The latest version of Angular CLI (v11.2) introduced a breaking change. The latest version of Wallaby now fully supports Angular CLI v11.2.
For VS Code and JetBrains editors, Wallaby’s Test Story Viewer now allows you
to quickly identify and hide repeated sequences of executed code pieces with the
codelens action: Hide repeated entries like this.
intention action: Hide repeated entries like this.
action: Hide repeated entries like this.
action: Hide repeated entries like this.
This feature lets
you focus on the important parts of the executed code and helps you maintain focus.
Some examples of repeated code may be utility functions (such as a logger), code repeated in a loop, and frequently executed functions that are callbacks (such as array’s .filter, .map, .reduce, etc.).
Once the repeated pieces of executed code are hidden from the test story, Wallaby’s Time Travel Debugger will no longer step into the hidden pieces when moving forward and backwards through your code.
Wallaby now supports .svelte files, showing coverage and logged values inside script blocks.
Please note that if you have any preprocessors (e.g. TypeScript) then you will need to ensure that source maps are available for them and enabled in your Svelte configuration in order to get correct coverage and line indicators.
