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

On update clear field for the subsequent dropdowns

Open
#248 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
frontend

Research direction

Start by tracing the course type, exact course, and slot dropdowns described in the issue, reproducing the stale-selection flow shown in Image 1. Verify that changing an earlier selection clears each subsequent field and that the refreshed dropdowns can be selected without clicking the X icon.

Written by the indexing model from the issue text.

Description

Problem

There is a minor inconvenience during the drop-down selection for the course type, the exact course, and the slot for it. The issue is that every time a user selects, for example, a new subject, the slot for the same subject does not appear. The user needs to go and click on the X icon, then remove the slot, click on it again, and then select a new slot. Same goes for course tag also. For example if a person goes from foundation course to discipline course, the previous course and the search bar are still appearing where you have to click on the x icon again.

image 1 gives more visual clarity on the issue

Image 1

Image

Solution

I'd propose a simple solution is that when a user selects another input field for either the course or course type or the course itself, the subsequent drop-downs clear the input field and the user can just click on it again as if it was a fresh input.

So if a user goes from a formational code to a discipline code, the subsequent dropdown for the course type and the slot clear themselves and the user can select the new subject or the slot as needed.

Dominant language
TypeScript
Stars
6
Forks
25
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 CodeChefVIT/ffcs

All issues in CodeChefVIT/ffcs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.