Properties UI allows to add custom values on strict vocabulary entries.
When the user types a value first and then selects a property key that belongs to a "strict" vocabulary term, the value doesn't get validated and the UI allows the user to enter it as a literal.
#3 Updated by Lucas Di Pentima 3 months ago
I've fixed several instances of the same bug at commit:arvados-workbench2|7d7a9bf - branch
17266-property-ui-synonym-fix, and also wrote an integration test that confirms it's correctly behaving.
Also added an optimization on Cypress tests that exposed a new bug that I'm trying to fix right now: when the details panel is open showing the collection version browser, sometimes renaming a collection changes the focus of the detail panel to show the collection's parent project information. This made a preexisting test fail.
#4 Updated by Lucas Di Pentima 3 months ago
Updates at arvados-workbench2|f75dc834 - branch
Test run: https://ci.arvados.org/view/Developer/job/developer-tests-workbench2/263/
- Fixed failing test described on the previous note.
yarn.lockwith the changes from updating cypress to 6.x on a previous branch.