-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XSD: the tool id attribute allows any string as per the schema definition #11196
Comments
Plus one for enforcing. |
As long as this is just a warning in the linter I think that's fine ... keep in mind that changing tool ids break tool lineages. |
Adding this restriction and providing an invalid As far as I know, it should not break any existing tool id, since this is only used when linting tools, but probably will mark |
I think so, since that means we can't update the tool for fixes. |
Oops... Understand! 😅 I will close this then :) |
I think we should lint tools like this, to avoid people adding more "tools with spaces in IDs". The old tools are then failing, that is another problem we should fix elsewhere, e.g. skipping lints in shed.yml ... but the correct thing is to warn users about a "wrong" ID, isn't it? |
I think David suggested the right thing here. The XSD linting doesn't allow this amount of flexibility. |
The current definition in the XSD file for the tool id attribute allows any string while the attribute documentation states:
and the IUC best practices recommendations states:
I propose adding a
<xs:simpleType>
with a pattern restriction that complies with these requirements. Or should the schema not enforce this rule to validate the XML document?The text was updated successfully, but these errors were encountered: