OpenRailAssociation / OpenRailAssociation/osrd
front: remove the selectedTrain and trainIdUsedForProjection from the store ?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 660
- Forks
- 87
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 269
Description
Description and goal
This information is currently stored in 3 different places in the application: in the store, in local storage and in the scenario url.
This information is fairly local, so we could do without it in the store. To be rediscussed.
Acceptance criteria
The code is cleaner
Contributor guide
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
Start by tracing where selectedTrain and trainIdUsedForProjection are read and written in the store, local storage, and scenario URL. Clarify whether the information can be kept local without breaking scenario URL behavior or persistence. Done means removing the duplicated store state and leaving the code cleaner, but the acceptance criteria need refinement first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100