Rename symbol implicitly imported from internal library in TypeScript
up vote
0
down vote
favorite
I have a module where I'm using Element class implicitly imported from the "dom" internal library.
However, in the same module I want to define an Element class of my own. This of course leads to a name collision and a world of pain.
is there a way to rename the implicit Element class from the DOM library?
Ideally, I would like something like this:
import * as DOM from 'dom'; // <-- what do I write here?
class Element { // <-- my element
private element: DOM.Element; // <-- reference to the original DOM element
}
typescript import rename
asked Nov 21 at 18:17
Slava Fomin II
9,9971166128
add a comment |
up vote
0
down vote
favorite
I have a module where I'm using Element class implicitly imported from the "dom" internal library.
However, in the same module I want to define an Element class of my own. This of course leads to a name collision and a world of pain.
is there a way to rename the implicit Element class from the DOM library?
Ideally, I would like something like this:
import * as DOM from 'dom'; // <-- what do I write here?
class Element { // <-- my element
private element: DOM.Element; // <-- reference to the original DOM element
}
typescript import rename
asked Nov 21 at 18:17
Slava Fomin II
9,9971166128
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a module where I'm using Element class implicitly imported from the "dom" internal library.
However, in the same module I want to define an Element class of my own. This of course leads to a name collision and a world of pain.
is there a way to rename the implicit Element class from the DOM library?
Ideally, I would like something like this:
import * as DOM from 'dom'; // <-- what do I write here?
class Element { // <-- my element
private element: DOM.Element; // <-- reference to the original DOM element
}
typescript import rename
asked Nov 21 at 18:17
Slava Fomin II
9,9971166128
I have a module where I'm using Element class implicitly imported from the "dom" internal library.
However, in the same module I want to define an Element class of my own. This of course leads to a name collision and a world of pain.
is there a way to rename the implicit Element class from the DOM library?
Ideally, I would like something like this:
import * as DOM from 'dom'; // <-- what do I write here?
class Element { // <-- my element
private element: DOM.Element; // <-- reference to the original DOM element
}
typescript import rename
typescript import rename
asked Nov 21 at 18:17
Slava Fomin II
9,9971166128
asked Nov 21 at 18:17
Slava Fomin II
9,9971166128
asked Nov 21 at 18:17
Slava Fomin II
9,9971166128
asked Nov 21 at 18:17
Slava Fomin II
9,9971166128
asked Nov 21 at 18:17
Slava Fomin II
9,9971166128
9,9971166128
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The only solution I've found so far is to define a custom type pointing to the original DOM symbol:
type DOMElement = Element;
namespace Acme {
class Element {
private element: DOMElement;
}
}
The idea here is to hide my custom Element class inside of a namespace and reference the DOM Element indirectly using custom type.
However, a better approach would be highly appreciated.
answered Nov 21 at 18:28
Slava Fomin II
9,9971166128
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The only solution I've found so far is to define a custom type pointing to the original DOM symbol:
type DOMElement = Element;
namespace Acme {
class Element {
private element: DOMElement;
}
}
The idea here is to hide my custom Element class inside of a namespace and reference the DOM Element indirectly using custom type.
However, a better approach would be highly appreciated.
answered Nov 21 at 18:28
Slava Fomin II
9,9971166128
add a comment |
up vote
0
down vote
The only solution I've found so far is to define a custom type pointing to the original DOM symbol:
type DOMElement = Element;
namespace Acme {
class Element {
private element: DOMElement;
}
}
The idea here is to hide my custom Element class inside of a namespace and reference the DOM Element indirectly using custom type.
However, a better approach would be highly appreciated.
answered Nov 21 at 18:28
Slava Fomin II
9,9971166128
add a comment |
up vote
0
down vote
up vote
0
down vote
The only solution I've found so far is to define a custom type pointing to the original DOM symbol:
type DOMElement = Element;
namespace Acme {
class Element {
private element: DOMElement;
}
}
The idea here is to hide my custom Element class inside of a namespace and reference the DOM Element indirectly using custom type.
However, a better approach would be highly appreciated.
answered Nov 21 at 18:28
Slava Fomin II
9,9971166128
The only solution I've found so far is to define a custom type pointing to the original DOM symbol:
type DOMElement = Element;
namespace Acme {
class Element {
private element: DOMElement;
}
}
The idea here is to hide my custom Element class inside of a namespace and reference the DOM Element indirectly using custom type.
However, a better approach would be highly appreciated.
answered Nov 21 at 18:28
Slava Fomin II
9,9971166128
answered Nov 21 at 18:28
Slava Fomin II
9,9971166128
answered Nov 21 at 18:28
Slava Fomin II
9,9971166128
answered Nov 21 at 18:28
Slava Fomin II
9,9971166128
9,9971166128
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53418296%2frename-symbol-implicitly-imported-from-internal-library-in-typescript%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
