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

Feature request: A way to hide an approved extension from the search results #6011

Open
microbit-carlos opened this issue Nov 15, 2024 · 2 comments

Comments

@microbit-carlos
Copy link
Collaborator

microbit-carlos commented Nov 15, 2024

Is your feature request related to a problem? Please describe.
We currently have an approved extension (pxt-micrbit-ml), which to be useful needs additional files to be injected by a different environment that embeds MakeCode.
So, this extension doesn’t offer any usable functionality on its own, and doesn't make much sense for a normal MakeCode user to add it to their project.

Describe the solution you'd like
It would be useful to have something like a flag in pxt.json file, to be able to hide an extension from the search.

Describe alternatives you've considered
There is already a hidden key in PackageConfig, but it must have a different purpose as it didn't work in our tests.
https://github.com/microsoft/pxt/blob/v11.3.1/localtypings/pxtpackage.d.ts#L82

We also tried removing the for PXT/microbit metadata from the extension README file, but that didn't work either.

In this case the extension needs to be approved, as it contain an editor extension as well, so removing it from the approval list would not be an option.

Additional context
N/A

@ramseyball
Copy link

Try this in your pxt.json

    "hidden": true,
    "searchOnly": true,

microbit-carlos added a commit to microbit-foundation/pxt-microbit-v2-power that referenced this issue Dec 6, 2024
@microbit-carlos
Copy link
Collaborator Author

microbit-carlos commented Dec 6, 2024

Thanks @ramseyball!
I've just tested it with an approved extension and it still appears on the search (and adding the extension to a project links to the latest version, which does include the changes in pxt.json). So it looks like this might need to be implemented in pxt/pxt-microbit.

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

No branches or pull requests

3 participants