Add protected strategy. #17
Merged
Conversation
This file contains 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
|
Hey @whatasunnyday, i like it! I used to have a request like this before. Will merge it ;) thanks! |
antek-drzewiecki
added a commit
that referenced
this pull request
Feb 3, 2015
Add protected strategy.
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.
Hello Antek,
I had to send a new PR because I force pushed. For my API, every end point is protected. I wanted to keep my code dry so I created a new strategy that by default protects every end point. I've updated the documentation to include an example. Let me know if there's any interest in this PR. If it's unneeded, feel free to leave it unmerged.