Yadciel/taskcafe
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
f45e359402
taskcafe/go.mod

32 lines
1.0 KiB
Modula-2
Raw Normal View History

chore: rename Citadel to Taskcafe
2020-08-07 03:50:35 +02:00
module github.com/jordanknott/taskcafe
initial commit
2020-04-10 04:40:22 +02:00
go 1.13
require (
refactor: replace refresh & access token with auth token only changes authentication to no longer use a refresh token & access token for accessing protected endpoints. Instead only an auth token is used. Before the login flow was: Login -> get refresh (stored as HttpOnly cookie) + access token (stored in memory) -> protected endpoint request (attach access token as Authorization header) -> access token expires in 15 minutes, so use refresh token to obtain new one when that happens now it looks like this: Login -> get auth token (stored as HttpOnly cookie) -> make protected endpont request (token sent) the reasoning for using the refresh + access token was to reduce DB calls, but in the end I don't think its worth the hassle.
2021-04-29 04:32:19 +02:00
github.com/99designs/gqlgen v0.13.0
feat: add notification UI showPopup was also refactored to be better
2020-08-13 03:54:14 +02:00
github.com/RichardKnop/machinery v1.9.1
feat: add seed command to generate fake project data
2021-01-05 23:46:15 +01:00
github.com/brianvoe/gofakeit/v5 v5.11.2
initial commit
2020-04-10 04:40:22 +02:00
github.com/go-chi/chi v3.3.2+incompatible
refactor: replace refresh & access token with auth token only changes authentication to no longer use a refresh token & access token for accessing protected endpoints. Instead only an auth token is used. Before the login flow was: Login -> get refresh (stored as HttpOnly cookie) + access token (stored in memory) -> protected endpoint request (attach access token as Authorization header) -> access token expires in 15 minutes, so use refresh token to obtain new one when that happens now it looks like this: Login -> get auth token (stored as HttpOnly cookie) -> make protected endpont request (token sent) the reasoning for using the refresh + access token was to reduce DB calls, but in the end I don't think its worth the hassle.
2021-04-29 04:32:19 +02:00
github.com/go-chi/cors v1.2.0
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
github.com/golang-migrate/migrate/v4 v4.11.0
initial commit
2020-04-10 04:40:22 +02:00
github.com/google/uuid v1.1.1
feat(MyTasks): allow filtering by task complete status
2021-01-04 00:04:15 +01:00
github.com/jinzhu/now v1.1.1
initial commit
2020-04-10 04:40:22 +02:00
github.com/jmoiron/sqlx v1.2.0
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
github.com/lib/pq v1.3.0
feat: redesign project sharing & initial registration redesigned the project sharing popup to be a multi select dropdown that populates the options by using the input as a fuzzy search filter on the current users & invited users. users can now also be directly invited by email from the project share window. if invited this way, then the user will receive an email that sends them to a registration page, then a confirmation page. the initial registration was always redone so that it uses a similar system to the above in that it now will accept the first registered user if there are no other accounts (besides 'system').
2020-10-21 01:52:09 +02:00
github.com/lithammer/fuzzysearch v1.1.0
refactor(Magefile): add build info in backend:build through ldflags
2020-12-30 02:37:14 +01:00
github.com/magefile/mage v1.11.0
feat: add seed command to generate fake project data
2021-01-05 23:46:15 +01:00
github.com/manifoldco/promptui v0.8.0
feat: redesign project sharing & initial registration redesigned the project sharing popup to be a multi select dropdown that populates the options by using the input as a fuzzy search filter on the current users & invited users. users can now also be directly invited by email from the project share window. if invited this way, then the user will receive an email that sends them to a registration page, then a confirmation page. the initial registration was always redone so that it uses a similar system to the above in that it now will accept the first registered user if there are no other accounts (besides 'system').
2020-10-21 01:52:09 +02:00
github.com/matcornic/hermes/v2 v2.1.0
feat: add pre-commit hooks & refactor code to pass linting
2020-08-21 01:11:24 +02:00
github.com/pelletier/go-toml v1.8.0 // indirect
cleanup: refactor api architecture & add user roles
2020-07-05 01:02:57 +02:00
github.com/pkg/errors v0.9.1
feature: add web & migrate commands
2020-07-16 01:20:08 +02:00
github.com/shurcooL/vfsgen v0.0.0-20180121065927-ffb13db8def0
initial commit
2020-04-10 04:40:22 +02:00
github.com/sirupsen/logrus v1.4.2
feature: add web & migrate commands
2020-07-16 01:20:08 +02:00
github.com/spf13/cobra v1.0.0
feature: remove sidebar & redesign top navbar
2020-06-23 22:20:53 +02:00
github.com/spf13/pflag v1.0.5 // indirect
feature: add web & migrate commands
2020-07-16 01:20:08 +02:00
github.com/spf13/viper v1.4.0
refactor: replace refresh & access token with auth token only changes authentication to no longer use a refresh token & access token for accessing protected endpoints. Instead only an auth token is used. Before the login flow was: Login -> get refresh (stored as HttpOnly cookie) + access token (stored in memory) -> protected endpoint request (attach access token as Authorization header) -> access token expires in 15 minutes, so use refresh token to obtain new one when that happens now it looks like this: Login -> get auth token (stored as HttpOnly cookie) -> make protected endpont request (token sent) the reasoning for using the refresh + access token was to reduce DB calls, but in the end I don't think its worth the hassle.
2021-04-29 04:32:19 +02:00
github.com/vektah/gqlparser/v2 v2.1.0
feat: add notification UI showPopup was also refactored to be better
2020-08-13 03:54:14 +02:00
golang.org/x/crypto v0.0.0-20200709230013-948cd5f35899
feat: add task activity
2020-12-19 03:34:35 +01:00
gopkg.in/alexcesaro/quotedprintable.v3 v3.0.0-20150716171945-2caba252f4dc // indirect
feat: redesign project sharing & initial registration redesigned the project sharing popup to be a multi select dropdown that populates the options by using the input as a fuzzy search filter on the current users & invited users. users can now also be directly invited by email from the project share window. if invited this way, then the user will receive an email that sends them to a registration page, then a confirmation page. the initial registration was always redone so that it uses a similar system to the above in that it now will accept the first registered user if there are no other accounts (besides 'system').
2020-10-21 01:52:09 +02:00
gopkg.in/mail.v2 v2.3.1
initial commit
2020-04-10 04:40:22 +02:00
)
Reference in New Issue Copy Permalink