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

Filter by parameter defined in API which are not object property

Open
#322 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
react, typescript
Domain
frontend

Research direction

Start by inspecting the schemaAnalyser and the code that builds the filter list, focusing on why modificationRestrict is excluded when it is absent from object properties. Reproduce the behavior with a custom API filter, then confirm that an API-defined non-property parameter is shown appropriately without hiding valid filters.

Written by the indexing model from the issue text.

Description

Hello,

We have a custom filter defined on our API, the parameter name is modificationRestrict and not rely on a property. I see that the code hide this filter because the schemaAnalyser doesn't find it in the properties list. I don't understand why this choice has been made, but it's seems this restrict to much the admin.

As I don't know if this is a bug or a design choice and consequently a feature request, I send a support question.

Dominant language
TypeScript
Stars
516
Forks
134
No merged PRs in 30d

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.

More from api-platform/admin

All issues in api-platform/admin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.