Sector occupancy limit lines
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- frontend
Research direction
The payload names no files or tests, so start by finding where the occupancy bars and their limit lines are rendered. The issue is a design question: limits should be pre-filled per sector combination and editable by hand, and the yellow/red line semantics are still undecided. Agreeing on that model with maintainers comes before any code. Done means the agreed design is written down and a follow-up issue or pull request is scoped from it.
Written by the indexing model from the issue text.
Description
Arvid:
Vi har kapacitetsvärden för varje godkänd sektorkombination som underlag för när vi ska öppna (visas som streck på
occupancystaplarna) men de säger inte alltid hela sanningen. Även om Peakvärdet för 23W45 är 19 kan man ibland sitta med 25st utan att det är några problem och andra dagar börja svettas redan vid 15
Something to implement, similar to in TopSky, having the opportunity to change the limit value manually, but also having them pre-filled depending on the sector combination.
There are yellow and red lines, some have only yellow, some none, difference?
- Ideally the lines are not static but react to the sector combination in use -> MM K manned separately gives higher limit than if MM K is covered by MM 2
- Possible issue with having combinations not specified in IRL capacity values
Originally posted by @maxlk96 in https://github.com/minsulander/vatiris/issues/17#issuecomment-2523068098
- Dominant language
- Vue
- Stars
- 13
- Forks
- 7
- Avg merge
- 23h 1m
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 minsulander/vatiris
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
minsulander/vatiris#194 ·
-
Add foreign ED+EK areas to AUP parserPossibly taken @maxlk96 claimed this 2 days ago. Openenhancement
minsulander/vatiris#195 · 1 assignee ·
-
bug
Difficulty 3/5 Half a day Newbie friendliness 45/100
minsulander/vatiris#185 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 18/100
minsulander/vatiris#184 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
minsulander/vatiris#183 ·
All issues in minsulander/vatiris
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Northeastern-Electric-Racing/FinishLine#4660 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
akitaonrails/FrankMD#268 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
marmelab/atomic-crm#401 ·
Maintainers usually reply within 1 day
-
account: profile
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day