cloudfoundry / cloudfoundry/stratos

Filter services marketplace by tag and user crafted queries

Open
#2,956 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

community triage
Dominant language
TypeScript
Stars
267
Forks
137
Avg merge
5h 14m
Merged PRs (30d)
77

Description

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"

image

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
    image
  • disabling / editing of currently active filters:
    image
  • inserting a new filter using a query syntax
    image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the services marketplace page and inspect how service tags are currently displayed and how marketplace results are loaded. Define the filter interaction and query syntax from the proposed tag, provider, and plan examples, then verify that filters can be shared through permalinks and that the displayed results update correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular, typescript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.