-
Notifications
You must be signed in to change notification settings - Fork 16
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
Remove partial
shorthand _p
and deprecate p
#39
Remove partial
shorthand _p
and deprecate p
#39
Conversation
@@ -24,12 +24,19 @@ def with_nice_partials_t_prefix(lookup_context, block) | |||
end | |||
end | |||
|
|||
require "active_support/deprecation" | |||
NicePartials::DEPRECATOR = ActiveSupport::Deprecation.new("1.0", "nice_partials") |
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.
@andrewculver not sure what version number we want in here, could be something in the 0.x
range too. Your pick 😄
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.
1.0 is good. That’s where we’re heading for sure.
Looks like the backtrace is getting tripped up I'll give it one shot and then just recommend swapping to |
e304d9c
to
f281083
Compare
Meh, can't figure out and it might be something with an interaction in the depending libraries that real apps might not see. |
* Rename `content` to `partial` Fixes #36 We're keeping the `_p` and `p` for now, to decide on separately. * Remove `partial` shorthand `_p` and deprecate `p` (#39) * Cut _p shorthand trial short by my own hands * Deprecate p shorthand in favor of partial Co-authored-by: Kasper Timm Hansen <kaspth@gmail.com>
Fixes #36
By default the deprecator logs to the console, put for ferreting errant
p
calls in CI, users could swap to raising: