Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Subscriber Billed Topics #609
Subscriber Billed Topics #609
Changes from all commits
d686e1e
28b654a
fb2fa4c
6bfe4a9
7c5b9c0
c6b64df
b9badee
36685e9
1655f58
bc3d897
0e4044b
ce7d447
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 know I said to just replace
v
in an older comment, but the more I think about it, the more I think that this is literally just about rate limiting, right? So maybe maybe ourBillee
is just avrate
(= visitor used for rate limiting), and for all the rate limiting functions, we'd usevrate
, but for everything else, we'd usev
?I have also noticed that you haven't tackled the
limitRequests
middleware at all. The rate limiting for number of messages (visitor-message-daily-limit
) and number of emails (visitor-email-limit-*
) happens inhandlePublish*
, but the rate limiting for requests (visitor-request-limit-*
) happens inlimitRequests
, so this logic would have to happen there, not here.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 did this using context (as suggested below), but isn't that supposed to be an anti-pattern? In any case, I guess it's just one thing so it shouldn't matter much. I feel like the ideal solution to this would be making
visitor
an interface and having acompositeVisitor
in addition to visitor...but, that's probably overengineering.