Question: what does this service provide that you do not get by simply importing d3 directly? about d3-ng2-service HOT 4 CLOSED

A few considerations to explain:

• The intent was to access D3 idiomatically as a service which is instantiated as a singleton.
• A primary concern was, where D3's event handling is used, the live link to the d3.event, if used, should not accidentally broken.
• The service was written, before the bundle definitions for the standard D3 bundle could be published on DefinitelyTyped/@types.
• The service is not an exact replica of the D3 standard bundle, e.g. d3-request is omitted in favour of using Angular for http.
• The intent was to have something for rapid prototyping, rather than a perfectly tailored minimal d3 feature set for a specific project.

All in all, if you are mindful of the event handling in D3 vs Angular and the cross-module prototype extensions used in D3, you are able to directly import the required functionality.

It kind of depends on exactly what D3 features you use.

That, in a nutshell, was the main background. 😄

from d3-ng2-service.

@impankratov Thanks for the suggestion, I will consider an expanded "intended use" section.

from d3-ng2-service.

Ok, thanks for the explanation

from d3-ng2-service.

@tomwanzek maybe this description could be added to the readme file? I think that could help people to quickly and easily understand the purpose of this project.

from d3-ng2-service.