-
Notifications
You must be signed in to change notification settings - Fork 60
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
Extending native JavaScript objects is a bad practice #47
Comments
mauteri
added a commit
to mauteri/liquid.js
that referenced
this issue
Dec 21, 2015
Added pull request that just sets |
ghost
mentioned this issue
Mar 9, 2016
I hit this issue too... would be an easy merge. May I ask why this has not been accepted? |
Ok.. so it seems to be fixed in master. Are there any known issues in master? |
Yeah, whats the status of this issue? |
Project looks pretty much abandoned to me... Last commit was December 5, 2016... :-/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed in a few spots that JavaScript's native
Array
andString
objects are being extended by Liquid withclear
,first
,last
, etc.With Liquid on our site, we ran into some pretty nasty bugs due to this and had to roll code back. Is there a reason this needs to be done as a property rather than creating helpers for this functionality? I'd be happy to provide a pull request to change this bit of code.
The text was updated successfully, but these errors were encountered: