API Center Portal - Predefined Choice-based filters broken
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
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
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
I have at least one test API where "None" is selected, but selecting the equivalent description in the filter yeilds no results:
Reproduction steps
Steps to reproduce the behavior:
- Create a custom predefined choice metadata field
- Make sure one or more assets have the field populated with an expected value
- Make sure the metadata item is exposed in portal under "Portal Settings" tab
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/api-center
-
Feature request Untriaged
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Azure/api-center#96 ·
-
Feature request Untriaged
Difficulty 5/5 Over a week Newbie friendliness 48/100
Azure/api-center#93 · 1 comment ·
-
Bug Untriaged
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Azure/api-center#92 · 1 reaction ·
-
Bug Untriaged
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Azure/api-center#91 · 1 comment ·
-
Feature request Untriaged
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Azure/api-center#90 · 1 comment · 1 reaction ·
All issues in Azure/api-center
Similar issues
-
area: capture good first issue priority: P2 type: defect
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jiegui2025/hwspec#51 ·
Maintainers usually reply within 1 day
-
[Feature]:Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
thephpleague/commonmark#1159 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Uuriko/project-room#1554 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
EchoTools/nevr-runtime#117 · 2 comments ·
Maintainers usually reply within 1 day