Resolve "Add model for planning of courses (dependend on ValidityRange)" #98
No reviewers
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!98
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "2-add-model-for-planning-of-courses-dependend-on-validityrange"
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?
Closes #2
There is an interface in cursus that is a supertype of courses which you could implement, so that we wouldn't need this additional type.
See:
https://docs.graphene-python.org/en/latest/types/interfaces/
https://edugit.org/AlekSIS/onboarding/AlekSIS-App-Cursus/-/merge_requests/2/diffs#a81fc04014516b978c11ae4b968d93b6d93e1dec_0_62
I think this would be the better way to do this (and would probably also require less work in the magnet board)
wouldn't this also require defining an additional type as can be seen in the graphene docs?
I don't understand what you mean
added 1 commit
78d36d1e- Actually save and sort modified course config dataCompare with previous version
added 2 commits
bd0eee36- Add column for subject2cc36737- Remove unneeded methodsCompare with previous version
added 2 commits
f83b711d- Allow creating and updating course configs2947619d- Specify fields for timebound course config mutationsCompare with previous version
added 3 commits
9af3ef14- Fix creating/editing course configs when switching between validityrangesc243f06b- Prevent duplicate courses in table94808f58- Only show classes of a pre-selected grade in course config rasterCompare with previous version
added 4 commits
521a8dd7- Re-add mutation to create timebound course configc43cc570- Beautify course config raster and differentiate teacher selectionb2e25c85- Add model and form extensions for assigning lesson quotas to teachers1a8aa626- Fix typoCompare with previous version
added 23 commits
1-frontend-for-modelsdbba2166- Add missing docstrings38cf45c6- Add status field to ValidityRange modela6c69da1- Fix managers84ad45ed- Skip recurrences if there are no recurrencesdcf4f581- Fix version in pyproject.toml51659d20- Rename Break to BreakSlotf3c962e0- Merge branch 'models' into 'master'1bf54e78- Merge branch 'master' into 2-add-model-for-planning-of-courses-dependend-on-validityrange2e955c6d- Fix migration historyCompare with previous version
added 1 commit
f8081833- Fix bugs with queryset and rename Break to BreakSlotCompare with previous version
Set
fieldsexplicitly for all queries/mutations.FIXME
added 57 commits
1-frontend-for-modelsde4decc5- Merge branch '1-frontend-for-models' into...6a97051f- Reformateea6bf35- Fix lintCompare with previous version
marked this merge request as ready
mentioned in commit
3df2b59cf3created #24 to continue this discussion
mentioned in issue #24