Implementation of express rate limiting middleware #32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ables and the query AST
evanmcneely
changed the title
milos381
approved these changes
Jun 2, 2022
shalarewicz
approved these changes
Jun 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This is the implementation of the rate limiting middleware. Tests are not working because typeComplexityAnalysis is not implemented in this branch. I am making issues to account for any error handling left undone and all aspects that need to be extended.
Type of Change
Issues
Evidence
No evidence. Tests are still in review ,and most of them are integration tests, so the middleware won't work without the algorithms still needing to be written.