Make context object available to exposures via matching keyword param #119
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
Since `context:` is a reserved keyword param for `View#call` anyway, and since exposure dependencies already implicitly have the context (since they're Part objects by that point), it should be no harm to make the context available for those who want to use it directly when building their exposures.
|
Super-cool @timriley 😄 |
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.
Since
context:is a reserved keyword param forView#callanyway, and since exposure dependencies already implicitly have the context (since they're Part objects by that point), it should be no harm to make the context available for those who want to use it directly when building their exposures.@waiting-for-dev What do you reckon? :)