API Center Portal - Predefined Choice-based filters broken

未关闭
#95 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
azure
领域
api, frontend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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

主要语言
PowerShell
星标
47
派生
21
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

Azure/api-center 的其他 Issue

查看 Azure/api-center 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。