Skip to content

Conversation

@lneves12
Copy link

@lneves12 lneves12 commented Feb 2, 2019

I am not sure we should support this here, because it's a deprecated format as we can see here: https://docs.npmjs.com/files/package.json#license so libraries should just adapt to it.

However, since there is no harm on having it, it could be nice to support that old format.

Reference: CodeSeven/toastr#604

@unindented
Copy link
Contributor

As you say, there's no harm. Thank you for your contribution!

@unindented unindented merged commit b3f7fe5 into microsoft:master Feb 3, 2019
@emmenko
Copy link
Contributor

emmenko commented Feb 6, 2019

Ah nice, I just bumped into this problem as well and was about to open a PR to fix this 😇

Is a bugfix release planned anytime soon?
Thanks! 🙏

@unindented
Copy link
Contributor

@lneves12 @emmenko just published 0.0.8 with these changes!

@emmenko
Copy link
Contributor

emmenko commented Feb 6, 2019

Oh wait, I think this is not entirely fixed.

In my case, a package has this format

image

So it's like singular license as an object. But this PR checks for package.licenses only. I can spin up a new PR to make the check more robust.

@lneves12
Copy link
Author

lneves12 commented Feb 6, 2019

What a big mess it was before they implement the new rule to follow SPDX format :P I didn't notice that case was possible too. Indeed, it would be nice to have it more bullet proof ;)

@emmenko
Copy link
Contributor

emmenko commented Feb 6, 2019

Sure, no worries 😉 I just opened a PR and added some tests. Have a look please 😇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants