Call custom get_by/2 context method
#343
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
|
👍 |
danschultzer
force-pushed
the
get-by-refactor
branch
3 times, most recently
from
df3953b
to
894dd75
Compare
danschultzer
force-pushed
the
get-by-refactor
branch
3 times, most recently
from
1141f08
to
89f6f7d
Compare
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.
#308 (comment) is not possible with how Pow currently handles custom context. This is a potential solution, but I'll work a bit more on it as I'm not sure if it makes sense to call Operations module rather than handle custom context in the context module itself.
Resolves #371