Use get_or_create (or something similar) to handle course (bundles) without TCCs when getting them for timetable planning #64
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#64
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?
this may, for example, occur when courses are created after creating (but not publishing!) a validity range. currently, users are not properly informed about why these newly added courses don't appear in the planning process
assigned to @permcu
The current solution is incomplete. We decided that each course is bound by a tcc to a validityrange. Currently a tcc is implicityly created for each course in scope on validityrange-creation. If the course did not exist then, but is added later, no tcc will be created linking it to the validityrange.
Proposed solution:
Since tccs are only relevant during lesson-planning and part of lesrooster, course-creation has nothing to do with them. Instead we do a lesrooster only solution: When the course(-bundles) are queried for lesson-planning the query detects if there is no tcc and creates it if missing.
This is the right place to do this, because here validityrange and group are combined.
@hansegucker what do you think of it? Should I get working on it?
We should discuss this in the context of the TCC raster.
@hansegucker what do you mean with that?
unassigned @permcu