Resolve "Migrate to vue3 frontend" #69
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-Buelleten!69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "12-migrate-to-vue3-frontend"
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?
Information and screenshots
No further information have been provided.
Checklist
tox -e reformat,lintusedapps.pyandREADME.rstup-to-dateBackend checklist
Frontend checklist (mandatory with ~"part::frontend")
Closes #12
assigned to @yuha
marked the checklist item
tox -e reformat,lintused as completedmarked the checklist item Changelog updated/No update necessary as completed
marked the checklist item Documentation (incl. Screenshots) up-to-date as completed
marked the checklist item Copyright in
apps.pyandREADME.rstup-to-date as completedmarked the checklist item (Unit) tests for new feature/regression tests for bug fixes (only if useful) as completed
marked the checklist item Adhere to URL scheme as completed
marked the checklist item Tested with admin account as completed
marked the checklist item Use permissions for all GraphQL mutations as completed
marked the checklist item Use query optimizer for all GraphQL queries as completed
marked the checklist item Don't use inefficient DB queries as completed
added 1 commit
79beff38- Add copyrightCompare with previous version
marked the checklist item Screenshots are attached (mobile and desktop) as completed
marked the checklist item Tested on mobile, tablet, and desktop sizes as completed
added 2 commits
aa188261- Add toolbar title151f8b73- Make foreign url slide urls clickableCompare with previous version
marked the checklist item Tested with normal account (based on permissions) as completed
assigned to @hansegucker and unassigned @yuha
added 1 commit
bbf4896e- Fix routesCompare with previous version
@yuha Please fix lint.
added 1 commit
a2f549f4- ReformatCompare with previous version
resolved all threads
This shouldn't use option API.
This is also option API and should be composition API.
Composition API
Please drop the API URL here, it's not part of the frontend.
What's the purpose of those empty objects?
Year?
Year?
left review comments
changed this line in version 6 of the diff
changed this line in version 6 of the diff
changed this line in version 6 of the diff
added 1 commit
Compare with previous version
added 1 commit
f437de71- Use composition APICompare with previous version
i thought that would have been an unrelated change since has already been there
type and content don't exist as model fields – they are used to show information about the polymorphic objects that may be included in a slide query (such as type: "static content slide" or smth like that). displayGroup and order are listed there in order to guarantee a reasonable header order. i couldn't think of a better way of doing so
resolved all threads
changed this line in version 8 of the diff
changed this line in version 8 of the diff
added 1 commit
52a62e78- Use correct years in copyrightCompare with previous version
mentioned in commit
5a2f92f522