Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

API Center Portal - Predefined Choice-based filters broken

Open
#95 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
azure
Domain
api, frontend

Research direction

Start in the API Center portal through Portal Settings, reproduce the issue with a predefined choice metadata field, and inspect how the filter uses the selected description versus its value. Done means the filter shows both value and description distinctly, displays the selected value, and returns assets matching that value.

Written by the indexing model from the issue text.

Description

Bug Untriaged

Description

When exposing custom metadata fields (specifically predefined choices) to the portal, descriptions are used as values instead of values themselves. Selecting the option appears to filter by the description and will not find any results

Image

I have at least one test API where "None" is selected, but selecting the equivalent description in the filter yeilds no results:

Image

Reproduction steps

Steps to reproduce the behavior:

  1. Create a custom predefined choice metadata field
  2. Make sure one or more assets have the field populated with an expected value
  3. Make sure the metadata item is exposed in portal under "Portal Settings" tab
  4. Open portal, and attempt to filter on the metadata definition

Expected behavior

  • Value and description are shown for selection in the filter so there's clarity in what's being selected (e.g. value is in bold, or description is smaller text size, something to make them visually distinct)
  • On selecting a filter item the value is shown in the portal, and the assets are correctly filtered

Actual behavior

  • Only descriptions of items are displayed, no values
  • Resulting search appears to be looking for the value to be equal to the description (at least visually)
  • Filter doesn't show the expected API list

Screenshots

See above

Additional context

N/A

Dominant language
PowerShell
Stars
46
Forks
21
Avg merge
21m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from Azure/api-center

All issues in Azure/api-center

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.