Dashboard widget for SMART PLAN #340
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-Chronos!340
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/smart-plan-dashboard-widget"
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?
Can be merged when https://edugit.org/AlekSIS/official/AlekSIS/merge_requests/155 is merged.
changed milestone to %"2.0a2"
@nik, now you can review.
Please evaluate https://pypi.org/project/humanize/ instead
This should be in
models.pyfor auto-discovery to work properly (without abusing side-effects of admin site registration, which might not happen in cases like applying single-app migrations, etc.).Doesn't this have a lot of common code with the regular view funtion? If yes, duplicate logic should probably be factored out (or argued against ;)).
Oh, even https://docs.djangoproject.com/en/3.0/ref/contrib/humanize/ ;)
The issue with putting it into models.py is a circular import.
There is a lot of common code, that's true. But some part of this code can't be factored out. I will do some work on this.
Ok, that's great.
Which one?
from aleksis.apps.chronos.util.prev_next import get_next_relevant_day↓
from aleksis.apps.chronos.models import TimePeriodThat's why I always wanted the code in prev_next as class methods on TimePeriod, or something similar ;).
Yes, you are right. #65
added 6 commits
master0e0eacb4- Merge branch 'master' into feature/smart-plan-dashboard-widgeta7eb4dc1- Fix path of get_next_relevant_dayCompare with previous version
changed this line in version 3 of the diff
changed this line in version 3 of the diff
changed this line in version 3 of the diff
added 2 commits
4a199dc9- Move TimetableWidget to models.py9ecc6742- Use django.contrib.humanize instead of own functions for dashboard widgetCompare with previous version
added 2 commits
00fd4ba2- Refactor out a lot of stuff used by TimetableWidget and my_timetable both to...c5b23ddd- Add card action link "Go to smart plan" for dashboard widgetCompare with previous version
resolved all threads
Any progress?
merged
mentioned in commit
fd78dcd1e4