-
Notifications
You must be signed in to change notification settings - Fork 31
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
Dependencies with resolved CQs are still shown as restricted #20
Comments
There was a bug in the script that pulls the NPM id from the CQ description. I've fixed it. Try it now. |
@waynebeaton Many thanks. It works much better now, but we still have some missings. For example: 'npm/npmjs/@types/axios/0.14.0'
But we have https://dev.eclipse.org/ipzilla/show_bug.cgi?id=22386 |
I haven't quite figured out how to deal with "works with" dependencies. See #13. |
Thanks |
Dependencies with resolved CQs are still shown as restricted.
For example, we already have CQs for the following runtime dependencies:
attr-accept@1.1.3(CQ22348)
dom-helpers@3.4.0(CQ22349)
file-selector@0.1.12(CQ22350)
json5@1.0.1(CQ22351)
nan@2.14.1(CQ22352)
popper.js@1.16.1(CQ22353)
prop-types-extra@1.1.1(CQ22354)
react-dropzone@9.0.0(CQ22355)
vscode-languageclient@6.1.3(CQ22358)
warning@4.0.3(CQ22359)
They were resolved a week ago.
The next run of dash-license shows that dependencies are still rejected:
dash-licenses commit
b907560
Steps to reproduce:
The new file DEPENDENCIES will be created
The text was updated successfully, but these errors were encountered: