Upgrading projects to Hex 2.0
Hex 2.0 introduces powerful new features, including an all-new, reactive compute model. It also eliminates use of the
$ syntax for Input parameters.
Projects need to be upgraded to take advantage of these features. If you open a project created prior to Hex 2.0, you will be shown a dialog prompting a migration:
While most projects can migrate without issue, some may have variable name collisions coming from the stripping of the
$ from existing input parameters.
In the example below, Hex stripped the
$ from an input parameter
$clusters , but there was already an existing Python variable named
clusters, leading to a collision. Hex automatically suggests a re-naming as shown below: