Incorrect stacked bar rendering when final stack segment is missing

[gaardhus]

I'm trying to render a stacked bar chart, but I'm running into some rendering problems when I have "missing" data.

I think the culprit is that the top of the stack is tied to the last entry, which makes the rendering weird when that is missing. I've adopted the example from the documentation and removed some entries to showcase the issue.

<script lang="ts">
	import { BarChart } from 'layerchart';

	const wideData = [
		{
			year: 2019,
			apples: 3840,
			bananas: 1920,
			cherries: 960,
			grapes: 400
		},
		{
			year: 2018,
			apples: 1600,
			bananas: 1440,
			cherries: 960,
		},
		{
			year: 2017,
		},
		{
			year: 2016,
			apples: 820,
			bananas: 560,
			cherries: 720
		}
	];
</script>

<div class="h-[300px] rounded-sm border p-4">
	<BarChart
		data={wideData}
		x="year"
		series={[
			{ key: 'apples', color: 'var(--color-danger)' },
			{
				key: 'bananas',
				color: 'var(--color-warning)'
			},
			{
				key: 'cherries',
				color: 'var(--color-success)'
			},
			{
				key: 'grapes',
				color: 'var(--color-info)'
			}
		]}
		seriesLayout="stack"
		props={{
			xAxis: { format: 'none' },
			yAxis: { format: 'metric' },
			tooltip: {
				header: { format: 'none' }
			}
		}}
		legend
		renderContext="svg"
	/>
</div>

[techniq]

Hey @gaardhus 👋

This was fixed in 2.0.0-next.31.

• [BarChart] Improve 0 or small value display when using rounding #383
• fix(Bar): Clamp radius to width/height to not cause artifacts with small values (including 0) when rounding a single edge. Fixes #383 #610

I'd recommend bumping to the latest @next version (2.0.0-next.44) while you're at it to have the latest.

I feel like shadcn-svelte might install an older (possibly 2.0.0-next.27) by default, but could be wrong (as you're not the first person to ask this :)

Once we wrap up some big PRs I was going to take a look at the shadcn-svelte charts integration, as some things will be simpler (especially after #663).

[gaardhus]

Thank you for the quick answer! I had already bumped my local version to 2.0.0-next.44 from an earlier version, but I guess it hadn't updated in the actual browser section. It works as expected now, thank you and have a nice day.