You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We noticed an issue with our horizontal bar charts after upgrading Vega-Lite to the latest version. Doing some Git bisecting, we can tie the change to 5.16.1 which makes me think something is going on from #9135@kanitw perhaps you have some idea on what's going on?
For what it's worth, this chart is generated in Altair in Streamlit with a Y Offset (See streamlit/streamlit#9604).
I'll let @kanitw chime in with more details about the previous PR, but I'm curious about the use case for having yOffset without y encoding as in your example. Is there any advantage to this versus using y instead of yOffset, which makes the example look as desired?
@joelostblom Good question (And thanks for the fast response!). I reached out to the original poster of the issue for their reasoning since Streamlit just passes down the altair chart to vega-lite with minor modifications. The example seems like a toy example, so perhaps their use case will be more clear.
Without a y we should probably treat the y offset as y and show a warning. This could be done in preprocessing. But maybe the original poster had a case with both.
Bug Description
We noticed an issue with our horizontal bar charts after upgrading Vega-Lite to the latest version. Doing some Git bisecting, we can tie the change to 5.16.1 which makes me think something is going on from #9135 @kanitw perhaps you have some idea on what's going on?
For what it's worth, this chart is generated in Altair in Streamlit with a Y Offset (See streamlit/streamlit#9604).
The generated vega-lite spec is below.
Before (5.16.0)
After (5.16.1)
The text was updated successfully, but these errors were encountered: