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
{{ message }}
This repository has been archived by the owner on Jan 24, 2023. It is now read-only.
As the marketplace grows, it becomes useful for users to filter services by tags in the services marketplace page, and potentially other fields such as provider name, or free plans.
Context
Why is this change important to you? How would you use it?
This enables service authors to publish granular services (e.g. apis) which will includes 100s of services in the marketplace.
Users can then filter only services from a a set of criteria (e.g. single provider), and can share permalinks to the marketplace page with such filters.
Possible Implementation
A possible UX could be to have currently displayed tags become clickeable, which would trigger adding the tag to a list of filters such as "tag:api" "tag:sql"
This could potentially be extended in the future with filters against additional fields such as "provider:x" or "plan.free:true"
See screenshots below from kibana filters as an inspiration:
display of currently active filters
disabling / editing of currently active filters:
inserting a new filter using a query syntax
The text was updated successfully, but these errors were encountered:
Detailed Description
As the marketplace grows, it becomes useful for users to filter services by tags in the services marketplace page, and potentially other fields such as provider name, or free plans.
Context
Why is this change important to you? How would you use it?
This enables service authors to publish granular services (e.g. apis) which will includes 100s of services in the marketplace.
Users can then filter only services from a a set of criteria (e.g. single provider), and can share permalinks to the marketplace page with such filters.
Possible Implementation
A possible UX could be to have currently displayed tags become clickeable, which would trigger adding the tag to a list of filters such as "tag:api" "tag:sql"
This could potentially be extended in the future with filters against additional fields such as "provider:x" or "plan.free:true"
See screenshots below from kibana filters as an inspiration:
The text was updated successfully, but these errors were encountered: