Untis import #230
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
aleksis/AlekSIS-App-CSVImport!230
Loading…
Reference in a new issue
No description provided.
Delete branch "untis-import"
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?
what about subject colors?
Missing doc string
This is a breaking protocol change.
I am not sure this is guaranteedto work.
Why check this so late> Check it right at the start, and return before doing anything if the app is not installed.
Or don't even register the field type. Thinking of it, this field type should be defined in Lesrooster…
See above. It becomes ever clearer that there should not be app-specific logic in here.
Even more app-specific logic. Where will this get us if at some point we have 100 apps that benefit form custom CSV import logic?
Ok, breaking in the changelog
This isn't as easy as registering app-specific field types. Do you have an idea how to do this?
Ah, this works?
What do you mean?
Is there a reason for this change?
I agree.
Ok
Of course it does, and it's the correct way to handle numbers, instead of rows of string transformations.
model(). Is it guaranteed that any model class can be instantiated without any arguments?Readability (at least after you let black reformat it).
Yeah, ok, thanks. I actually have never questioned this function as I wrote it like seven years ago.
Yes, that's guaranteed. Saving isn't guaranteed.
Source?
Replace the legacy views with the new frontend ;).
But, what is this import used for in the first place?
For setting a related validity range in the importer for matching e. g. lessons to validity ranges.
In that case, the Lesrooster app should offer its own frontend for the CSV importer. While keeping the logic in the CSV, the validity range should be selected in a UI provided by Lesrooster.
Maybe the import can be parameterized through the URL? I.e., Lesrooster has a button in the validity range view to "Import data from CSV", and this links to CSVImport's job creation wizard, passing the validity range along in the URL? This mechanism should be agnostic of the semantics of the passed parameter, e.g. by storing the parameters in the import job, and letting the field type directly use the stored parameters in its logic.
https://docs.djangoproject.com/en/5.0/ref/models/instances/#creating-objects
changed this line in version 2 of the diff
changed this line in version 2 of the diff
changed this line in version 2 of the diff
added 3 commits
57d547fd- Tidy up changes39c5528a- Use Subject from Cursus everywhere1630905b- Update changelogCompare with previous version
added 1 commit
d82663f9- Migrate to RegistryObject for field typesCompare with previous version
changed this line in version 4 of the diff
added 1 commit
b65c7a18- Factor out some app-specific field typesCompare with previous version
added 1 commit
0d67ff9c- Add field type for creating users from usernameCompare with previous version
assigned to @hansegucker
unassigned @hansegucker
added 1 commit
cdc9c105- Don't fail on existign usersCompare with previous version
added 1 commit
0fa8389d- Fix username importCompare with previous version
added 1 commit
401e4733- Fix username importCompare with previous version
@hansegucker checks.
changed this line in version 9 of the diff
added 55 commits
masterad88cc21- Merge branch 'master' into untis-import21d848de- Fix compatibility with Core 4.0 and fix testsCompare with previous version
changed the description
changed this line in version 10 of the diff
changed this line in version 10 of the diff
added 2 commits
9963c5e0- Provide demo templated2023c90- Move import to new frontend and support additional params from other appsCompare with previous version
mentioned in merge request AlekSIS-App-Lesrooster!178
resolved all threads
Blocked by https://edugit.org/AlekSIS/official/AlekSIS-Core/-/merge_requests/1808
Correctly respect school term of groups for courses, also respect school term and validity range for lessons
added 3 commits
ee5c6fdc- Fix and improve import process after merge60955320- Also allow plain files for import0e86a312- Fix and adapt Untis importCompare with previous version
added 1 commit
c2188ffa- Update depsCompare with previous version
assigned to @hansegucker
mentioned in commit
7c9095a9af