-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refinements for Half Donut #441
Comments
What is the recommended workflow for development? Should I add a new Gallery example to test with? |
I think I'll start by adding a new entry to the list of things here in {
title: 'Donut: Empty Segments',
url: '/examples/Donut/Donut:%20Empty%20Segments',
duration: 0,
},
{
title: 'Donut Data Transitions',
url: '/examples/Donut/Donut%20Data%20Transitions',
duration: 0,
},
// New:
{
title: 'Half Donut',
url: '/examples/Donut/Half%20Donut',
duration: 0,
}, |
Or, maybe this is the place to add it: |
Hi @curran, thanks for your interest in contributing. We have a general contribution guideline here. |
Oh excellent! Thank you for the info. I've started on this here (very much WIP): #444 I hope this is the right place to start adding examples. It's currently in |
I think putting it under |
As a user creating a half-donut chart by specifying the
angleRange
ofVisDonut
to[-Math.PI / 2, Math.PI / 2]
, I want the vis to look decent and scale properly to its container, so that I don't end up with wasted screen real estate.Here's what it looks like now (note the gap below - which is a major problem):
Subtasks:
For offset in Y direction, we may need to add a parameter that gets used here:
https://github.com/f5/unovis/blob/main/packages/ts/src/components/donut/index.ts#L127
The text was updated successfully, but these errors were encountered: