WIP: Draft: Resolve "Migrate to new data model" #729
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
source::aleksolotl
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
aleksis/AlekSIS-App-Alsijil!729
Loading…
Reference in a new issue
No description provided.
Delete branch "246-roadmap-migrate-to-new-data-model"
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 #246
added 2 commits
73b75742- Adapt to Core 4.0 managed_by featureCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
620ca595- Add models for calendar-based data modelCompare with previous version
added 1 commit
a28e8ece- Add GraphQL schema for DocumentationCompare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 4 commits
0c7f38ac- WIP: Add permissions for Documentationcaddeaf6- Correct verbose namesf7dee2f0- Remove obsolete code1d404533- Return only documentations a user is allowed to viewCompare with previous version
added 2 commits
Compare with previous version
added 1 commit
Compare with previous version
changed title from Draft: Resolve "{-[ROADMAP] -}Migrate to new data model" to Draft: Resolve "Migrate to new data model"
Merge according to Dev Meeting decision
added 39 commits
master79517819- Add models for calendar-based data model52a9cd14- Add GraphQL schema for Documentation97e41acf- WIP: Add permissions for Documentation26b4e2b2- Correct verbose namesdd092e32- Remove obsolete codeb6701825- Return only documentations a user is allowed to view428c5a8c- Add some verbose names for new class register modelsfc19c951- Update models467aada0- Set mutation fields explicitlyCompare with previous version
changed this line in version 12 of the diff
added 2 commits
3fca9a1f- Fix lint9ea0ed66- Update models and fix migrationsCompare with previous version
shouldn't this field (and the two following ones) also be set to
null=TrueNo, it's a CharField and on such fields we only make use of blank=True (so we allow "", but not
None).TODO: Add color to
ExtraMarkand make it configurable whether an extra mark is shown in coursebookTODO: Add teacher field
added 1 commit
Compare with previous version
added 1 commit
1792cf1f- Add teachers field to documentationCompare with previous version
added 1 commit
eced46b8- Add color and show in coursebook fields to ExtraMarkCompare with previous version
This should be
amends.what do you mean by that?
A lesson event is the planned future. A documentation represents, what really happened (in this planned event). Because of this close relation (the lesson event and documentation are somehow the „same” logical event), the amends logic should be used.
This was - sadly - done in the coursebook branch, the respective changes should probably be cherry-picked into this branch somehow
@magicfelix
created #279 to continue this discussion
resolved all threads
mentioned in issue #279