HSLdevcom / HSLdevcom/digitransit-ui
[regression] Time(zone?) problems in digitransit-ui
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 267
- Forks
- 145
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 75
Description
Since approximatively two weeks, I have timing problems in digitransit-ui using master. Indeed, Before when I choosed to leave (or arrive) at 12:00 I had solutions arriving at that time. Now, they are proposed as if I choosed "14:00" as the time, and indeed, if I set time as "10:00", I get solutions for 12:00.
I used to comment timezone arguments in config file and that used to work, but it doesn't seem to work anymore.
Could you fix this?
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.
Research direction
No file, test, or entry point is named. Reproduce the regression on master by comparing 12:00 and 10:00 departure or arrival searches, then trace the timezone configuration and time handling until the selected time produces solutions for that same time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100