Skip to content
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

noConflict #3

Closed
dtex opened this issue Sep 17, 2013 · 2 comments
Closed

noConflict #3

dtex opened this issue Sep 17, 2013 · 2 comments

Comments

@dtex
Copy link

dtex commented Sep 17, 2013

I'd like to add a basic noConflict() utility method that provides the same functionality as http://underscorejs.org/#noConflict This can of course be accomplished outside of json-path, but I just thought it would be nice to have available.

In my case I'm using json-path in a CMS so I have to keep everything out of the global namespace to avoid conflicts. I loathe JSON traversal so it's likely that I would use it in a site that is managed by my CMS and I don't want to set myself up for version conflicts in the future.

If you're cool with this, I'll submit a pull request.

@ghost ghost assigned flitbit Sep 30, 2013
@flitbit
Copy link
Collaborator

flitbit commented Oct 4, 2013

I previously had an incomplete #noConflict implementation in the code -- this issue brought it back to my attention. Thank you. I completed it and pushed (v0.1.3) to npm. Also note that I committed release versions (uglifyjs, minifies).

If you have any other issues come up I welcome forks & pull requests as well.

Cheers. ~P

@flitbit flitbit closed this as completed Oct 4, 2013
@dtex
Copy link
Author

dtex commented Oct 4, 2013

Cool, thanks!

@flitbit flitbit removed their assignment Oct 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant