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.

Sign up for GitHub

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

Jump to bottom

improve license detection for built-in extensions #7381

Open
akosyakov opened this issue Mar 20, 2020 · 0 comments
Open

improve license detection for built-in extensions #7381

akosyakov opened this issue Mar 20, 2020 · 0 comments
Labels
enhancement issues that are enhancements to current functionality - nice to haves help wanted issues meant to be picked up, require help vscode issues related to VSCode compatibility vsx-registry Issues related to Open VSX Registry Integration

Comments

@akosyakov
Copy link
Member

Currently we always try to look into LICENSE file, but there can be more locations including configurable.

Form @spoenemann:

  • If a package.json has SEE LICENSE IN ..., then try there first
  • after that try LICENSE.md, LICENSE, and LICENCE.txt in this order
@akosyakov akosyakov added enhancement issues that are enhancements to current functionality - nice to haves help wanted issues meant to be picked up, require help vscode issues related to VSCode compatibility vsx-registry Issues related to Open VSX Registry Integration labels Mar 20, 2020
@vince-fugnitto vince-fugnitto mentioned this issue Mar 27, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement issues that are enhancements to current functionality - nice to haves help wanted issues meant to be picked up, require help vscode issues related to VSCode compatibility vsx-registry Issues related to Open VSX Registry Integration
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@akosyakov