-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add cllient handler for installing one package #99
Comments
That is easy as just insert Install link :) But what exactly do you mean? Why it is in npm-packager repository? |
I do not ask how to install another package. I propose to add such ClientHandler that gets specific package name in parameters and shows that packagae's badge with install button like there is a badge for specific track in spotify as I showed above |
@FreePhoenix888 where it should be shown? In which cases? |
It should not be shown. It should be as function which can be called in any other package which uses it Imagine it like react component in library that is used by 1+ packages instead of writing the same code again in these 1+ packages |
@FreePhoenix888 why not use Or maybe you need something like this deep-foundation/deeplinks#262? Or you're talking about a standard way to install all packages visually when need? But how we know that package is needed? |
@Konard , it looks like you are kidding me. I want to have client handler that lets me to have ui to install one specific (or a few) packages, like I can do with spotify that lets to have badge for one specific audio Where have I said not to use ClientHandler? It anyway uses another client handler which is actually a function that returns react component I sincerely do not understand why you do not understand me with such spotify example pinned |
Description
See how discord show spotify embed links:
Just imagine, there is this song badge on Spotify. Now imagine that I want to add a badge of my specific one song to my website. I take the "embed" link to this badge and paste it onto my site. Now users can click play a song or even go to spotify.
I don’t have to create such a component myself, it’s already provided by Spotify
Now imagine the same situation. I don't want to type out the package installation badge many times in different packages where it could potentially be required frequently. I want a client handler to appear in npm packager that can be used in any other, and this client handler will provide just such a badge. You pass it a badge for which packages you need through arguments, and you receive such a badge
Is it clear now? those. in simple words - I don’t want to insert packager ui into my tiny client handler so that the user can search for the required package and download it. I want a small badge with the name of the package and a button to install
I started to wonder because potentially an application or package could have the ability to offer to download a specific package
Which is not directly dependent
That is, there is a client handler for chatgpt azure, and it requires you to connect the model, and in the popover it tells you that “psss, if there is a ready-made package that already has ready-made models, you can just download it.” But it would be even cooler if the user in this popover also had a badge of this package and downloaded it with one button
Tell me it's cool
Same issue with deep memo. The logger is not required, but you can download and enable it, and it would be nice to have some kind of single standard badge instead of copying it from project to project
Requested Solution
Add such client handler that provides badge for one or more packages
The text was updated successfully, but these errors were encountered: