Skip to content
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

fix: move to the new version of nodejs-lockfile-parser #288

Merged
merged 1 commit into from
Dec 5, 2018

Conversation

yuliabaron
Copy link
Contributor

@yuliabaron yuliabaron commented Dec 3, 2018

  • Ready for review
  • Follows CONTRIBUTING rules
  • Reviewed by Snyk internal team

What does this PR do?

Projects with no name property in package.json will now be named by their relative path

What are the relevant tickets?

https://snyksec.atlassian.net/browse/SC-6758
Also related to snyk/nodejs-lockfile-parser#29 and
snyk/npm-deps#53

@yuliabaron yuliabaron self-assigned this Dec 3, 2018
Copy link
Contributor

@Kirill89 Kirill89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need also to pass file name as last argument of parse function.

@miiila
Copy link
Contributor

miiila commented Dec 4, 2018

@Kirill89 is right

@yuliabaron yuliabaron force-pushed the lockfile_parser_return_valid_name branch 2 times, most recently from 6e4eb50 to 37dcacb Compare December 4, 2018 13:25
@Kirill89
Copy link
Contributor

Kirill89 commented Dec 5, 2018

LGTM. But would ask also @miiila to take a look.

@justshiv
Copy link

justshiv commented Dec 5, 2018

@yuliabaron this is the ticket I was referring to in Boost - would like to bump the version to https://github.com/snyk/nodejs-lockfile-parser/releases/tag/v1.9.1 if you're okay with that

Copy link
Contributor

@miiila miiila left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yuliabaron I believe this should be a fix commit as we are fixing a bug, when we were not able monitor project without a name. Also wording of a commit could reflect the outcome, as it will be shown in released notes (see https://github.com/snyk/nodejs-lockfile-parser/releases/tag/v1.9.1).

@yuliabaron yuliabaron changed the title feat: move to the new version of nodejs-lockfile-parser fix: move to the new version of nodejs-lockfile-parser Dec 5, 2018
@yuliabaron yuliabaron force-pushed the lockfile_parser_return_valid_name branch from 37dcacb to 0387444 Compare December 5, 2018 13:05
@yuliabaron yuliabaron merged commit e0b524d into master Dec 5, 2018
@yuliabaron yuliabaron deleted the lockfile_parser_return_valid_name branch December 5, 2018 13:30
@snyksec
Copy link

snyksec commented Dec 5, 2018

🎉 This PR is included in version 1.114.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants