Rename symbol implicitly imported from internal library in TypeScript
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
add a comment |
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
add a comment |
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
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 '18 at 18:17
Slava Fomin IISlava Fomin II
10.2k1268132
10.2k1268132
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
add a comment |
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.
add a comment |
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.
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 '18 at 18:28
Slava Fomin IISlava Fomin II
10.2k1268132
10.2k1268132
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.
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