Fix misspell
Fix sorting tasks with null values
Fix sorting by priority for postgres
Merge branch 'master' into feature/position
Add community link
Update golang.org/x/crypto commit hash to 44a6062 (#429)
Update golang.org/x/crypto commit hash to 44a6062
Reviewed-on: vikunja/api#429
Update module lib/pq to v1.4.0 (#428)
Update module lib/pq to v1.4.0
Reviewed-on: vikunja/api#428
Fix updating position
Add ordering tasks in buckets by position
Make task sort by string
Merge branch 'master' into feature/position
Update golang.org/x/crypto commit hash to 3c4aac8 (#419)
Update golang.org/x/crypto commit hash to 3c4aac8
Reviewed-on: vikunja/api#419
Merge branch 'master' into feature/position
Fix moving tasks back into the empty (ID: 0) bucket
Add adding a default position when creating new tasks
Update golang.org/x/crypto commit hash to a76a400 (#411)
Update golang.org/x/crypto commit hash to a76a400
Reviewed-on: vikunja/api#411
Remove unused code
Fix tests
Add migration for position attribute
Add position attribute
Co-authored-by: kolaente <k@knt.li>
Co-authored-by: renovate <renovatebot@kolaente.de>
Reviewed-on: vikunja/api#412
Fix not returning errors
Fix integration tests
Add more tests
Make task filtering actually work
Change tests
Fix using filter conditions
Fix test
Remove unused fields
Fix static check
Remove start and end date fields on task collection
Fix misspell
add filter logic when getting tasks
Add parsing filter query parameters into task filters
Start adding support for filters
Co-authored-by: kolaente <k@knt.li>
Reviewed-on: vikunja/api#243
Remove traces of unix timestamp
Revert renaming reminder table column
Fix staticcheck
Remove unused table call
Add migration for renaming reminders table
Fix issues with using TimeStamp
Fix lint
Updated all created / updated fields to use TimeStamps
Add comments
Convert all created / updated fields to datetime
Add time util package
Co-authored-by: kolaente <k@knt.li>
Reviewed-on: vikunja/api#130
There was a bug where it would return all tasks with a true value before the ones with a false value. This is the exact opposite of what the db does, leading to wrongly sorted values
