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

[Feature Request]: Request to disable free text typing in the property-filter form after selecting the operator.

Open
  • Is something wrong?
#3,601 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the Cloudscape PropertyFilter component API and the token editor behavior described in the issue, especially how custom value forms are provided. Identify where an option to hide or disable inline value entry would fit; done means users can require values to be entered through the custom form without arbitrary typing in the inline field.

Written by the indexing model from the issue text.

Description

enhancement
Description

Description:
Currently, in the Cloudscape PropertyFilter component, after a user selects a property and an operator, the value field beside the operator allows free text typing, even when a custom form is provided for value entry. This allows users to bypass custom validation and logic implemented in the custom form, leading to inconsistent or invalid filter tokens.
Use Case:
We have scenarios where the value for a filter must be selected or validated through a custom form (e.g., dropdown, multiselect, or date picker). Allowing users to type arbitrary values directly into the inline value field beside the operator defeats the purpose of custom validation and can result in invalid or unsupported filter tokens.
Requested Feature:
Please provide a way (such as a prop or configuration option) to disable or hide the inline free text value input beside the operator in the PropertyFilter token editor, so that users are required to enter values only through the provided custom form.
Benefit:
This feature would ensure that all filter values are validated and consistent, improving data integrity and user experience. It would also allow developers to fully control the value entry process for each property/operator combination.

Code of Conduct
Dominant language
TypeScript
Stars
2.7k
Forks
248
Avg merge
3d 14h
Merged PRs (30d)
83

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 cloudscape-design/components

All issues in cloudscape-design/components

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.