HSLdevcom / HSLdevcom/digitransit-ui

Settings for transport mode preferences should be visible from the start

Open
#5,207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
267
Forks
145
Avg merge
1d 15h
Merged PRs (30d)
75

Description

Description:

Currently, the settings for selecting preferred transport modes (e.g., bus, bike, car) are only visible after a route request has been made. These preferences should be accessible directly in the initial settings without requiring the user to initiate a route search.


Steps to reproduce:

  1. Open the application.
  2. Observe that transport mode preferences are not available on the initial screen.
  3. Make a route request to view and adjust the transport mode settings.

Observed behavior:

Transport mode preferences are only visible after submitting a route request.

Expected behavior:

Transport mode preferences should be displayed in the initial settings, allowing users to adjust their preferences before performing any route searches.


Screenshots:
image
image


Additional information:

Making transport mode preferences visible from the start improves usability and allows users to customize their experience more intuitively.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start at the initial settings screen and trace how transport mode preferences are rendered after a route request. Compare the two states and identify the existing preference controls. Done means bus, bike, car, and other available transport preferences are visible and adjustable before any route search.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.