Filtering Dropdown Selection List Prior To Searching
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
No file, test, or entry point is named. Start by locating the TypeScript component that renders the related-table dropdown and tracing how filtering works before and after typing; done should keep Active records selectable, exclude Inactive records from new selections, and preserve archived values.
Written by the indexing model from the issue text.
Description
Hey Mark,
Currently, the filter field seems to primarily function as a search tool, which is useful, but I require pre-typing filtration.
Let's say in the related table, we have columns named 'Company Name' and 'Status'. Ideally, before a user starts typing, the dropdown list should already be filtered to display only items where the status is 'Active'.
For instance, let's consider a scenario with three records in the related table:
Company Name | Status
Amazon | Active
Google | Active
Apple | Inactive
If a user attempts to search for 'Apple', they shouldn't retrieve any results, and it shouldn't appear in the dropdown because it's marked as Inactive.
Deleting inactive items from the related table isn't feasible since we need to preserve historical data in archived records. Thus, when an item becomes 'Inactive', users shouldn't be able to select it in future records, but any archived record retaining that value should remain unchanged.
Do you have any suggestions on how to accomplish this?
With much gratitude,
Paden
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 markcunninghamuk/PCF_Library
-
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 30/100
markcunninghamuk/PCF_Library#26 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
markcunninghamuk/PCF_Library#25 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
markcunninghamuk/PCF_Library#23 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in markcunninghamuk/PCF_Library
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·