uber/react-vis

LabelSeries with Stacked Vertical Bar Series

Open

#1037 opened on Nov 13, 2018

View on GitHub
 (4 comments) (2 reactions) (0 assignees)JavaScript (8,615 stars) (868 forks)batch import
bughelp wanted

Description

Hi, I have some issues with labelSeries when using it with a vertical Bar Series (so stackby="y"). The label seem to always go way above the bars like that:

image

I've done a codepen to show my problem. https://codesandbox.io/s/5kx21nk77l

Is there a way to get around the problem or maybe i'm doing this the wrong way (i used this tutorial ) ? I've tried negative values and reverse the labelSeries position in the XYplot but i don't have consistent result ...

Contributor guide

Tech stack
reactjavascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
React basicsreact vis basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue demonstrates a label positioning bug when using LabelSeries with stacked vertical Bar Series (stackBy='y'). The user provided a codesandbox (https://codesandbox.io/s/5kx21nk77l) and a screenshot. Investigate the react vis source code, particularly the LabelSeries component and its interaction with the stackBy prop. Check if there are any changes in the library since 2018 that may have fixed or altered this behavior. Look at the XYPlot and BarSeries components to understand how label positions are calculated for stacked bars. Consider proposing a fix that adjusts label offset for stacked bars. The issue is old and may require revalidation with the current version.