-
Notifications
You must be signed in to change notification settings - Fork 133
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
Usage of import
as method names
#380
Comments
Hi @martines3000, we can't because this method name is prescribed by http://rdf.js.org/stream-spec/ Perhaps monkey patching (there exist npm tools for this) might help you out. |
@RubenVerborgh I am already doing that, but it is quite tedious as I need to patch multiple libraries and rebuild a some of them. Is there maybe a way to raise the issue to the specification writers, as I think it is also not a good practice to use “reserved” keywords like that as method names? |
Indeed; the spec repository is part of this GitHub organization, would be good to raise it there. |
Hi. We are developing a project that is running inside a hardened JavaScript environment called SES (Secure EcmaScript) and this library is one of our sub-dependencies. SES doesn't allow overriding “reserved” keywords like
import
and this causes many issues for us.My question is if it would be possible to maybe rename methods like this:
N3.js/src/N3Store.js
Line 305 in 51a4156
from
import(stream)
to something like_import(stream)
. This would solve our problems.Thank you for the help.
The text was updated successfully, but these errors were encountered: