-
Notifications
You must be signed in to change notification settings - Fork 7
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
Implement referrer api #500
Conversation
7621548
to
4ade2f0
Compare
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.
I have looked at everything except for the internal/api
part, and that stuff looks good. Can you please move the DB model changes and the stuff that fills these fields into a separate PR? i.e. everything not in internal/api
. I would like to see these fields being filled first before we expose them in the API.
10f7336
to
1747bd1
Compare
ea2e960
to
1e54a81
Compare
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.
I pushed some commits to fix nitpicks; otherwise the implementation looks good. Please also add test coverage for the new endpoint, then we're good to go here.
This looks like a query that is going to be very costly if we have to sequence-scan the table.
951d2ba
to
5252078
Compare
5252078
to
fe6bc01
Compare
No description provided.