Closed gauthiergodart closed 4 months ago
Thanks a lot for reporting your problem with using parenthesis in the "Csub" string.
While reproducing your scenario the schema check for the
Thanks for your answer. It is kind of weird, because the PDSC schema check never complained with this on our side. What is the version of the schema you have been using? The pack we are maintaining is not publicly released yet.
From the schema, version 1.7.31, parenthesis are actually accepted:
<!-- Component Sub Name Type -->
<xs:simpleType name="CsubType">
<xs:restriction base="xs:string">
<xs:minLength value="0" />
<xs:maxLength value="32" />
<xs:pattern value="([A-Za-z0-9]{1}[A-Za-z0-9_+():/\- \.]*)?"></xs:pattern>
</xs:restriction>
</xs:simpleType>
Sorry, my fault. I have used "(" as the first character in Csub="(custom)"
which is not allowed.
I checked that the CMSIS-Toolbox deals with parenthesis in Csub
correctly.
The Software Components View needs to be looked at.
Hi @gauthiergodart, thanks for reporting this. We've found the issue in the Software Components view and a fix will come in the next release.
Hi @mcgordonite, thanks a lot for the update. Feel free to get back to me if I can be of further assistance.
The fix was just released in version 1.25.0 of the extension.
Perfectly working now, thank you
Type: Bug Report
Describe the bug
When a component is defined into the PDSC with parenthesis in a Csub tag (e.g. Csub="Test (parenthesis)"), a bug occurs when one try to select the corresponding component via the Software Components view in VS Code: the component appears selected for a few seconds, but then, it is automatically unchecked. The dependencies of the component are not signaled to the user, and the user gets the feeling the component could not be selected. But, in the cproject.yml file, the component is actually referenced. In other words, there is a bug in the parser used in background, which fails to handle parenthesis into Csub tags from a pdsc file. This bug also reveals wrong error handling: the user is not informed of the issue, and the project remains in a kind of undefined state, with the component being actually added to the environment, without having its dependencies met, and without the user being aware of it.
To Reproduce Steps to reproduce the behavior:
Expected behavior
The component should be actually selectable, and its dependencies should be checked