Curran Kelleher

Great to hear from you @jasondavies !!! I must say I'm a huge fan of your work. This contribution looks amazing.

But overall, the source maps don't seem to be working. For example, when I add this change: I get this error: The source maps don't seem to be doing their...

Scaffolded by @rokotyan in * https://github.com/ExaForce/unovis/pull/2 As I start working on this, I'm wondering how we want to support hierarchies. I see there's already some precedent for hierarchies with the...

Working through how to manage the exports

Interestingly, the import _does_ actually resolve at Runtime, but the TypeScript linting system can't seem to resolve it.

Thanks for having a look! After I run `npm run build:ts`, the error still shows for the import from `'@unovis/react'`. I have a feeling it might be related to the...

The error persists even after running `npm run build:react`. I think the core issue is that VSCode/TypeScript is resolving the import to `node_modules`.

An interesting question arises when we compare this to nested donut - do we want the ability to label intermediate nodes? Or do we want to just label the leaf...

It did in the [Exaforce Unovis fork](https://github.com/ExaForce/unovis/tree/1.5.0-exaforce), yes! I just surfaced the same changes as a PR agains this repo as well: * https://github.com/f5/unovis/pull/556

Yes! Here is a description of the problem, phrased as a user story: > As a developer new to Unovis, I want to be able to use the VSCode [Go...