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
One thing we should do to improve the “IDE story” is to surface the concept of services to users.
What we seem not to want to do: “Here is a monolithic package that installs a bunch of stuff you don't understand.”
What we should probably do instead: “The ide-typescript package provides these services; let's help you find packages to consume them.”
Two obvious improvements:
Tell users when they're searching for service consumers/providers
The service and serviceType search params are useful, but a search results page that uses those params doesn't have anything on the page to distinguish it from an ordinary package listing. Here's how we could fix that:
(Through working on this, I discovered pagination counts are wrong; filed this issue.)
Tell users when a package consumes/provides services
On a package detail page, we can enumerate the services provided and consumed. For instance, if a package provides the foo service, foo would be a link to a search results page that filters on packages that consumefoo.
A couple ways we could present this:
What benefits does this feature provide?
Explained above.
Any alternatives?
No, I think this is the best option. We want to be able to tell users “here's how you can do X” without privileging one particular package over others. “Here are all packages that can do X” is a good way of doing that. The user can make judgments based on download counts, on the presence of “Made for Pulsar!” badges, or whatever else.
Other examples:
No response
The text was updated successfully, but these errors were encountered:
Overall, this is a fantastic suggestion, and I really like the way your made the mockup for the sidebar here, which I honestly think should be the way we go about adding this new information.
Plus, it'd be a great idea to expose the ability for users to actually search for these parameters, although the search on the website is still lacking, so maybe that isn't the highest priority.
If you have the mockup HTML to share that'd be rad, otherwise I'll take a look at implementing this sidebar, unless anyone beats me too it, thanks!
Have you checked for existing feature requests?
Summary
One thing we should do to improve the “IDE story” is to surface the concept of services to users.
What we seem not to want to do: “Here is a monolithic package that installs a bunch of stuff you don't understand.”
What we should probably do instead: “The
ide-typescript
package provides these services; let's help you find packages to consume them.”Two obvious improvements:
Tell users when they're searching for service consumers/providers
The
service
andserviceType
search params are useful, but a search results page that uses those params doesn't have anything on the page to distinguish it from an ordinary package listing. Here's how we could fix that:(Through working on this, I discovered pagination counts are wrong; filed this issue.)
Tell users when a package consumes/provides services
On a package detail page, we can enumerate the services provided and consumed. For instance, if a package provides the
foo
service,foo
would be a link to a search results page that filters on packages that consumefoo
.A couple ways we could present this:
What benefits does this feature provide?
Explained above.
Any alternatives?
No, I think this is the best option. We want to be able to tell users “here's how you can do X” without privileging one particular package over others. “Here are all packages that can do X” is a good way of doing that. The user can make judgments based on download counts, on the presence of “Made for Pulsar!” badges, or whatever else.
Other examples:
No response
The text was updated successfully, but these errors were encountered: