✅Release 2.0.7

Release 2.0.7 was published to the Chrome Web Store on August 12, 2024

Action Required by August 26th: upcoming changes to PixieBrix Mod Development in 2.1.0

In the next release, 2.1.0, all mods you’ve built will require a mod id. To simplify the transition, we’ll be automatically updating the mods on your account to have an assigned id. However, some users may need to take action. For more information, see the release notes Release 2.1.0

🎨 User Experience

• Output keys are now optional in the runtime and Page Editor to reduce noise from unsed outputs (#8949, #8950)

• Handle undefined condition values in the runtime (required for passing potentially undefined variables directly as a condition). Warn on if-else conditions that are constants (#8946)

• Add a "duplicate element" button to the Document Builder design view. This allows developers to duplicate elements within the container (#8947)

• Consolidated the "Context" and "Rendered" Data Panel tabs into the new "Input" tab, defaults to "Arguments". Consolidated "Ouput" and "Preview" tabs under the "Output" tab, defaults to "Latest Run". Renamed the "Preview" tab to "Design" for the Form and Document Builders. (#8895)

• Updates the tab name in the Mod Options form from "Preview" to "Design" for consistency with the Data Panel (#8985)

• Adds affordance to add new starter bricks directly to an existing mod (#8916)

🐛 Bug Fixes

• Fixed issue preventing the logs from being displayed in the Page Editor (#8971)

• Fixed issue causing the sidebar to be stuck in a perpetual loading state if a sidebar tab was missing a tab title (#8981)

🧱 Updated Bricks

• Show Sidebar Brick now defaults to forcePanel=true, existing mods will not be impacted. When forcePanel=false and the Mod Launcher is the focused tab, the panel will be shown instead (#8987)