Getting d3.event about d3-ng2-service HOT 6 CLOSED

Thanks for the take. I do not seem to experience the problem so far. The associated demo I built in tomwanzek/d3-ng2-demo and the live github page for a few reference components seems to handle the events as expected.

The injected service singleton seems to work alright in the project generated from the angular-cli webpack version (1.0.0-beta.11-webpack.8. with some dependency fixes for typescript and awesome-typescript-loader.)

Did you experience a different event-handling use case, where you saw the live-binding issue?

from d3-ng2-service.

Hmm I need to recheck, maybe it was fixed in one of the patches

from d3-ng2-service.

No I still have the problem but I import directly from d3-selection in a vendor.ts files that is bundled for all my modules, maybe that's the problem, I don't create a new instance of the d3 lib for each component

from d3-ng2-service.

Try writing it as a service, that way you have a singleton, which is created once and that is the one you pull in. Feel free to look at the source code in the repo, I always just pull directly from the import that feeding the service.

Another possible explanation could have to do with which module system the TS code is compiled to. I matched mine essentially to the one used by angular-cli. But, if one goes commonjs, say, that might lead to a different experience with d3.event.

from d3-ng2-service.

I'm closing this issue. If you experience the issue using this service, let me know and I will reopen it. Cheers.

from d3-ng2-service.

Yup, no prob :)

from d3-ng2-service.