You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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.
@microbit-carlos why approve it if you don't want it to be in search. That is the only additional feature approved extensions have unless you specify the category. I am not sure I understand this feature request.
One possible use case could be a "dependency only" extension that could be useful to have approved, so that it can take advantage of features like the extension being cached. For example, pxt-ws2812b is a dependency to pxt-neopixel, it currently appears on the search, but when the user selects it it doesn't load any blocks, which can be confusing.
But, in this specific case, this ticket was raised for CreateAI. The ML extensions cannot do much without the CreateAI editor injecting the model and additional info into a project, so it doesn't make sense for the user to load the ML extension on a normal MakeCode project from the extension search screen.
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 inPackageConfig
, 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
The text was updated successfully, but these errors were encountered: