-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(repository): use generic cacheable function #271
feat(repository): use generic cacheable function #271
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this is kinda nice, I like this. I do think we should be careful of using the IDs in the cache and potentially setting a different cache per resource. There are a handful of IDs in the database who are uniquely keyed on tuples like (tenantId, actionId)
for example. It would be easy to misuse this and start accidentally poisoning the cache.
a7a7995
to
d5b231a
Compare
8559aeb
to
6667919
Compare
ab37253
to
8179746
Compare
8179746
to
8559aeb
Compare
673d57f
to
6946884
Compare
5ccbbfb
to
14e599c
Compare
ea898c7
to
fa3166e
Compare
@@ -18,6 +18,7 @@ import ( | |||
) | |||
|
|||
func TestMessageQueueIntegration(t *testing.T) { | |||
t.SkipNow() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we skipping these tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
somehow these tests fail on my machine. pushed this by accident, good catch
Description
Fixes # (issue)
Type of change
What's Changed