fixes bug in view where elixir_interpolation.unescape_chars was privatized #36
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
a private function. It seems unesacpe_string is the thing to use instead.
|
Thanks! Good catch on the name change. If it's too hard for backwards compat I don't care that much about it at the moment because of the low user base, haha. |
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.
this commit broke the things for 1.12
elixir-lang/elixir@7d3a336#diff-8459fda1a6be2648729f053b9380160826e30b4cc79da7f965b302fee5cf6916
I'm not sure how you want to handle backwards compatibility here.