-
Notifications
You must be signed in to change notification settings - Fork 212
Fusesoc type #740
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
base: main
Are you sure you want to change the base?
Fusesoc type #740
Conversation
|
Putting aside the fact that we have not yet defined how the various test types are to behave (parse, build, roundtrip, base, advanced and so on), the test file seems to comprise 4 groups of parse, roundtrip and build test cases that are identical but for variations in namespace, name and version values. Why? A few tests meant to fail (there are none here) would be more useful and informative. |
|
Oh, I was just copying the format of the tests in some other type already present, taking that for an appropriate level of effort. I'll see about adding some more. |
pombredanne
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Here are a few nits for your review... also I am not sure that the encoding of the namespace / matches the spec... can you double check?
tests/types/fusesoc-test.json
Outdated
| "expected_failure_reason": null | ||
| }, | ||
| { | ||
| "description": "Build test for PURL type: fusesoc", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There may be an extra space there?
tests/types/fusesoc-test.json
Outdated
| "expected_failure_reason": null | ||
| }, | ||
| { | ||
| "description": "Build test for PURL type: fusesoc", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extra space in the description
types/fusesoc-definition.json
Outdated
| "version_definition": { | ||
| "requirement": "optional", | ||
| "native_name": "version", | ||
| "note": "The version is the semantic version of the fusesoc core. We would really like this to be required, but that breaks validation." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not sure you need this comment.... The fact that version is optional is a spec thing when you want to refer to a package without mentioning a version like in the CVE schema, or when using that with a VERS. What about this:
| "note": "The version is the semantic version of the fusesoc core. We would really like this to be required, but that breaks validation." | |
| "note": "The version is the semantic version of the fusesoc core." |
This change adds a type for FuseSoC cores (see https://github.com/olofk/fusesoc).