Eventually, I figured out the following workaround: put the names in a separate array (selectionNames in my case), put the code snipped below in the select, then elsewhere refer to selectionNames[imageSelect] to get the actual string.
Yea, that’s a bug in the Inputs notebook, which should escape the values when generating the HTML. Currently it’s using an html tagged template literal, but that doesn’t do any escaping.
In the near future, we’re planning to let you browse published versions, and we’d also like import statements to pin the current version automatically to prevent notebooks from breaking when their imported notebooks change.
Even greater would be to get notified when a imported notebook changes (release notes, #updates number in a red circle?).
Yet even greater would be if changes are upwards compatible so they don’t break your notebook. Incompatible changes may include help to best refactor or migrate to the latest version.
Maybe stick with the working revision by default and make upgrading optional?
Also, it seems like proper string processing should have no breaking side effects in code logic? I did not do a deepmdive into the changes, though.
That’s the goal with pinning version numbers by default. The plan is if you delete the pinned version number, it’ll automatically re-pin to the current latest version.