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

--readme-path is ignored by the marketplace #1048

Closed
winseros opened this issue Sep 3, 2024 · 9 comments · Fixed by #1062
Closed

--readme-path is ignored by the marketplace #1048

winseros opened this issue Sep 3, 2024 · 9 comments · Fixed by #1062
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@winseros
Copy link

winseros commented Sep 3, 2024

Hi, I created an extension and when packaging, I specified the path to the readme file --readme-path README.marketplace.md. The README.marketplace.md got included into the visx package and the package manifest points to it.

Having published the extension, I was surprised that Visual Studio Marketplace ignored the README.marketplace.md and shows the README.md from GitHub (!!) as a readme.

@benibenj
Copy link
Contributor

benibenj commented Sep 4, 2024

Thanks for reporting this. Could you check both the visual studio code marketplace website and the marketplace inside VSCode and let me know if you see the wrong readme in both cases?

@benibenj benibenj self-assigned this Sep 4, 2024
@benibenj benibenj added the info-needed Issue requires more information from poster label Sep 4, 2024
@winseros
Copy link
Author

winseros commented Sep 5, 2024

Hi, both the marketplace website and the Visual Studio Code show the wrong readme.

@benibenj benibenj removed the info-needed Issue requires more information from poster label Sep 5, 2024
@benibenj
Copy link
Contributor

benibenj commented Sep 5, 2024

What version are you currently using? Could you make sure you are using one of the latest versions, we made a fix in this area not to long ago, this might have fixed your case.

@benibenj benibenj added the info-needed Issue requires more information from poster label Sep 5, 2024
@winseros
Copy link
Author

winseros commented Sep 5, 2024

Hi, I'm not sure about the exact version. The packaging was done by a GitHub runner and vsce was obtained by npm install -g @vscode/vsce. So I assume it was the latest version available at the date I created the issue.

@benibenj benibenj removed the info-needed Issue requires more information from poster label Sep 5, 2024
@benibenj
Copy link
Contributor

benibenj commented Sep 5, 2024

Great, I'll have a look. In the meantime you can add readme.md to the .vscodeignore file. This will lead to it not being packaged in the extension.

@winseros
Copy link
Author

winseros commented Sep 5, 2024

README.md was not included into visx. Only README.marketplace.md was. That was surprising me especially, as the marketplace was using the readme file that was not even included into the visx.

@benibenj
Copy link
Contributor

benibenj commented Sep 5, 2024

There seems to be a bug in vsce. However, the github readme file also seems to be packaged and because it is using the default readme.md filename, it is being shown on the marketplace. The marketplace does not check github repositories for readme files.

@benibenj benibenj added the bug Issue identified by VS Code Team member as probable bug label Sep 6, 2024
@benibenj
Copy link
Contributor

benibenj commented Sep 6, 2024

Need to verify with feature owner what the expected behaviour is to understand if this is a marketplace bug or a vsce bug.
related: #905

@joaomoreno
Copy link
Member

I suggest we reverse our decision to keep the display README.md in its original location and instead just copy its contents over the top level README.md, keeping things simple.

benibenj added a commit that referenced this issue Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants