Frontend for Models #1
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Lesrooster#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stundenplanerstellung ("Magnettafel") offene Punkte (Zusammen mit @permcu und @yuha):
assigned to @ZugBahnHof
created branch
1-frontend-for-modelsto address this issuementioned in merge request !90
changed the description
TO FIX: In the TimeboundCourseConfig raster, courses with groups that are not associated with the school class group type and that are therefore not included in the group list of this component, break the component.
marked the checklist item Lessons sollen bearbeitbar sein (konfigureieren usw) as completed
@hansegucker what about this:
LessonBundle
TCCBundle
Let's think ...
TCCBundle →
groupis not necessary, because the courses have groups and the bundles should be by usable in all timetables which are affected.Same with validity range, as the validity range is set via the timebound course configs. Important: Check constraint that only allows one validity range in one bundle.
LessonBundle → As result, this needs to create single lesson objects.
TO DO: Allow for different slots for different groups of groups in the same validity range (e.g. grades 1-4 have 45-min lessons; and grades 5-10 have 60-min lessons). @ZugBahnHof could you please take a look at this?
(the FSS needs this, so please give it high priority)
how should this be done? Should slots only be valid for specific groups? or validity ranges? or something different?
marked the checklist item Stunden, die gleichzeitig stattfinden as completed
FIXME: Make time ranges in timetable raster period cards more compact
mentioned in commit
7e23691262