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

vsx-registry: fix the 'licenseUrl' link #8095

Merged
merged 1 commit into from
Jun 26, 2020
Merged

Conversation

vince-fugnitto
Copy link
Member

What it does

Fixes: #8094

The following pull-request fixes the licenseUrl link when attempting to open an extension's license from the vsx-editor.
Previously, the url was incorrect as it would refer to the local hosted path. If the data is available, use it directly to open the link.

Screen Shot 2020-06-25 at 8 48 32 PM

How to test

  1. open the 'extensions-view'
  2. perform the same test for a builtin, installed and search result extension:
    • open the extension's info (header & readme), click the license link and verify the link works correctly

Review checklist

Reminder for reviewers

Signed-off-by: vince-fugnitto vincent.fugnitto@ericsson.com

- fixes the `licenseUrl` link for builtin and installed extensions.

Signed-off-by: vince-fugnitto <vincent.fugnitto@ericsson.com>
@vince-fugnitto vince-fugnitto added bug bugs found in the application vsx-registry Issues related to Open VSX Registry Integration labels Jun 26, 2020
@vince-fugnitto vince-fugnitto self-assigned this Jun 26, 2020
@kittaakos
Copy link
Contributor

Nice, I have tried it with the electron example, and I could open the license in my OS browser 👍
When I open the license for this extension
Screen Shot 2020-06-26 at 12 40 51,
it opens the following URL: https://open-vsx.org/api/vscode/xml/1.46.1/file/LICENSE-vscode.txt
I do not understand the version difference between the VS Code extension and the link.

@vince-fugnitto
Copy link
Member Author

vince-fugnitto commented Jun 26, 2020

I do not understand the version difference between the VS Code extension and the link.

@kittaakos thank you for the review! Without the changes proposed in #8063, the API call to open-vsx will always return the newest (latest) version which is why you see an updated version present in the link. The same is true about other information such as the rating, readme, etc.

@kittaakos
Copy link
Contributor

he API call to open-vsx will always return the newest (latest) version which is why you see an updated version present in the link

👍 Follow-up: #8097

@kittaakos kittaakos self-requested a review June 26, 2020 12:14
Copy link
Contributor

@kittaakos kittaakos left a comment

Choose a reason for hiding this comment

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

I have verified it locally with the electron example; I could open the license for the built-ins in my OS browser. 👍

Copy link
Contributor

@lmcbout lmcbout left a comment

Choose a reason for hiding this comment

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

LGTM
Tested on Ubuntu 18.04 with Chrome.
Thanks @vince-fugnitto

@vince-fugnitto vince-fugnitto merged commit 3f42537 into master Jun 26, 2020
@vince-fugnitto vince-fugnitto deleted the vf/license-url branch June 26, 2020 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug bugs found in the application vsx-registry Issues related to Open VSX Registry Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vsx-registry: installed licenseUrl cannot be opened
3 participants