Updated: Dec 21, 2020
Welcome to v8.8.0, the 20X release of Bixby Developer Studio. This release includes the new Symbol Search feature, as well as minor fixes and enhancements.
Adding onto the Search & Replace feature, this release adds an option to search for "symbols" within
.bxb files. When searching symbols, Bixby searches specific locations within
.bxb files that allow defining or referencing symbols. Currently, the feature supports searching for concept or action names across files within the capsule. Over time this feature will include properties or other developer-defined variables.
Perform a symbol search by choosing "Symbol" instead of "Text" in the drop-down next to the search input.
All other search options are available while performing a symbol search including replace. Happy refactoring!
We've added a few new commands and editor actions relating to symbols.
From the editor in a
.bxb file, right-click on a concept or action name to Find All References of the symbol across the capsule. This command is also available with a keyboard shortcut (
F12) or from the command palette.
From the editor in a
.bxb file, right-click on a concept or action name and choose Go To Definition to navigate to the definition of the symbol. This command is also available with a keyboard shortcut (
F12) or from the command palette. Additionally, you can use the
Click on Mac) shortcut to quickly navigate to the definition.
The Simulator steps now show deleted steps. This change avoids confusion when exporting stories from the Simulator. Deleted steps cannot be returned to but are part of the conversation.
Hover over a node in the training graph to see a quick summary in the graph toolbar.
Updated: Nov 5, 2020
Welcome to v8.7.0, the 20V release of Bixby Developer Studio. This release includes minor enhancements and bug fixes.
In the Simulator, on the User panel in the left sidebar, you were able to decide whether the Simulator should remember permissions that the user has agreed to give, and other selections the user has made. This was previously called "Selection Learning", and by default it was enabled.
In this release, we've changed this option to Deterministic Mode, and it now functions the opposite way of Selection Learning. It is disabled by default. When it is enabled, no choices will be learned or stored, and the Simulator will predictably ask for permissions or other choices again every time. To export stories, you must enable this mode.
If you lose your network connection, there's a limit to how many times Bixby Studio will try to reconnect automatically. This is a safe-guard against using up system resources unnecessarily.
We've added a new control to allow you to manually reconnect after automatic retries fail. The new control is on the bottom status line of the main window, next to the Global Status Indicator in the lower left corner, and it appears after multiple automatic reconnection attempts fail.
We've added a number of additional submission error messages to help you understand which capsule permissions you are missing.
We've added tooltips for the buttons in the upper-right corner of the training entry display.
Updated: Oct 8, 2020
Welcome to v8.6.0, the 20T release of Bixby Developer Studio. This release includes enhancements for the Story Assertions, Debug Console, and the Quick Select.
We've introduced an improvement to the Story Assertions. You can add an assertion template called "Default Tests" to any step of a story to test it automatically.
When one or more assertions fail, you can click a button from the error view to update expected values in assertions that support it (such as those made with the new "Default Tests" template).
The "Update Expected Values" dialog allows you to preview and accept the suggested changes for your assertion failures, making the assertions pass on the next run.
Export Story in the Simulator now supports adding the "Default Tests" assertion to every step in your story, at the time it is created.
After your exported story runs the first time, a dialog window will appear to confirm the addition of the Default Test assertion file to every step.
You can also request the addition of an assertion file to every step in a story at a later time, for any story and template, from the context menu in the navigation bar.
We've added the ability to step through and view the minor version changes in the execution graph.
We've updated the Quick Select dialog to keep the most recently searched text, and improved the navigation of the commands.