Remove Unsafe Calls to Eval()

[michael-lumley]

closes #39

Fixes unsafe eval to comply with CSP.

I am using d3-organization-chart in my project, however the naked evals are unsafe and triggering CSP errors. I've updated to avoid use of eval in an unsafe way.

[bumbeishvili]

PR code does not replace functionality which eval does, so I have to close it

[michael-lumley]

PR code does not replace functionality which eval does, so I have to close it

@bumbeishvili Can you explain the missing functionality? A colleague and I are currently debating what the actual reason for doing the eval() is, and can't seem to figure it out.

[michael-lumley]

@bumbeishvili Wanted to check in and see what kind of timeline you had in mind here. We're trying to plan around whether we should expect this PR to merge or if we need to fix the problem further downstream. Thanks!

[bumbeishvili]

@michael-lumley It looks like you were right, I can go ahead and merge this PR right away.

[bumbeishvili]

@michael-lumley also note - I started working on the new version of the org chart (Not sure about the final timeline, since I am doing this, while I work on commercial projects involving org charts, not on my free time )

It will be based on the latest d3.v6 and it will include some new features which were often requested

https://observablehq.com/d/e106c59dbd9f6151

If you want to use it meantime, feel free - https://observablehq.com/d/e106c59dbd9f6151

Here is a list of features which will be implemented - #14

[michael-lumley]

@bumbeishvili Thank you!