You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say I have a tool with a CWL id of bwa--mem--0.7.17:
id: bwa--mem--0.7.17
If I open that tool in Rabix Composer, the double dashes will be converted to spaces:
I use Rabix Composer to change to something unrelated like the description and save the tool.
Observed
When I open the CWL file, its ID is now something different:
id: bwa_mem_0_7_17
Expected
I would expect the ID of the tool to remain as it was before I edited the unrelated field in Rabix. It should remain bwa--mem--0.2.17 and not change to bwa_mem_0_7_17.
The text was updated successfully, but these errors were encountered:
@pkerpedjiev-zymergen thank you for the report. I can reproduce and this is indeed unacceptable behavior. We will fix this in 1.1.0. We'll ping here in this report as soon as it gets to the master branch.
@pkerpedjiev-zymergen after a brief discussion on the CWL gitter I was pointed to a tightening up of the CWL specification that is imminent (in 1.1). In common-workflow-language/common-workflow-language#429 we plan to only allow ids that form valid javascript without quoting. This will mean no dashes and spaces amongst other things.
We will improve the RC documentation to reflect this. We could use this ticket to discuss the proper behavior for RC when a user types in an invalid id in the code pane.
Steps to reproduce
Let's say I have a tool with a CWL id of
bwa--mem--0.7.17
:If I open that tool in Rabix Composer, the double dashes will be converted to spaces:
I use Rabix Composer to change to something unrelated like the description and save the tool.
Observed
When I open the CWL file, its ID is now something different:
Expected
I would expect the ID of the tool to remain as it was before I edited the unrelated field in Rabix. It should remain
bwa--mem--0.2.17
and not change tobwa_mem_0_7_17
.The text was updated successfully, but these errors were encountered: