This PR changes the behaviour of how tasks are sorted. Before, the frontend would sort tasks but this resulted in some cases where tasks were not sorted properly. Most of this is test code to reliably reproduce the problem and make fixing it easier.
The actual bug was in Vikunja's api, therefore I've removed all sorting of tasks in the frontend and ensured the api properly sorts tasks.
Fixes https://github.com/go-vikunja/frontend/issues/54
Depends on https://kolaente.dev/vikunja/api/pulls/1177
Co-authored-by: kolaente <k@knt.li>
Reviewed-on: https://kolaente.dev/vikunja/frontend/pulls/1997
Reviewed-by: Dominik Pschenitschni <dpschen@noreply.kolaente.de>
Changes only in task detail view. Probably this should be done everywhere:
- some buttons were using the uppercase words consistently, some were not
- some were using articles, some were not => I removed them everywhere to shorten the label length
- some buttons were refering to the task, some were not. Since we are already in the context of the task (we are not the task detail page) I removed the reference everywhere.
The green button can be confusing because the wording "Done" can be interpreted as "done editing the task" or "the task should be marked as done". Changing the text in the button makes the description more precise.
Co-authored-by: David Morlitz <david@morlitz.com>
Reviewed-on: https://kolaente.dev/vikunja/frontend/pulls/1340
Reviewed-by: konrad <k@knt.li>
Co-authored-by: dmorlitz <david@morlitz.com>
Co-committed-by: dmorlitz <david@morlitz.com>
Wait until the request is finished
Wait for the newly created task exists in the dom
Wait until the login request is done
Wait until the list request is done
Make sure no user token is in local storage when trying to register
Make sure to always upload test results
Disable capturing videos of test runs in CI
Add uploading test result screenshots from ci
Assert a success notification is shown after creating a new list
Change input element locators
Fix testing for favorite lists
Make sure faked usernames are always random
Make sure the tests work
Make sure to use node 12 everywhere in ci
Add docs
Fix setting api url for running tests
Use a working node version
Ignore cypress screenshots and videos
Set cache folders
Explicitly ignore cypress files when running unit tests
Trigger Drone
Only run unit tests with yarn test:unit
Add serve dist command to serve built static files
Trigger Drone
Fix cypress image
Change cypress image
Unify test & build step back again to prevent double installation of dependencies
Add cache location config
Move test steps to separate pipeline
Run cypress tests in drone
Fix all tests
Make all factory methods static
Use factories everywhere
Cleanup
Add tests for the editor
Add tests for viewing link shares
Fix seed
Add test to make sure settings elements are hidden if the user does not have the right to edit the current list
Co-authored-by: kolaente <k@knt.li>
Reviewed-on: https://kolaente.dev/vikunja/frontend/pulls/313
Co-Authored-By: konrad <konrad@kola-entertainments.de>
Co-Committed-By: konrad <konrad@kola-entertainments.de>
