-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
🔨 remove default layer from chart configs / TAS-675 #4103
Conversation
Quick links (staging server):
Login:
SVG tester:Number of differences (default views): 0 ✅ Edited: 2024-11-11 17:17:25 UTC |
00ca4a3
to
520d3e6
Compare
d057b20
to
d3b015d
Compare
520d3e6
to
66f141f
Compare
d3b015d
to
a680591
Compare
66f141f
to
0de1405
Compare
a680591
to
8438f8a
Compare
0de1405
to
f753e3b
Compare
8438f8a
to
9bf41a6
Compare
f753e3b
to
cd4fc4f
Compare
9bf41a6
to
5da7000
Compare
cd4fc4f
to
c9de5c6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this! I have found one issue though and I'm not sure if this is because the admin does things differently now or if this is just a little bug or if I misunderstand how this is supposed to work.
Here is what I did:
- take a line chart (like this one) that does not currently have inheritance
- create a parent admin layer chart
- set a property to a non-default value (e.g. y column max) and save
- in the original standalone chart, refresh and check that the parent is now set
- go to the customize tab and click "bind to data" under y column max
I would expect the parent value to be in effect now but it is the default value. Am I wrong or is this a bug?
"Bind to data" means the y-column max is inferred from data, it essentially sets |
The label is maybe a bit confusing – maybe "Unset" would be clearer? |
c9de5c6
to
3c89b72
Compare
@danyx23 do you think you have time to finish this review in the next week or so? I think it would be good if my changes and especially Marcel‘s work on narrative views builds on this. |
Hey @sophiamersmann, thanks for the ping! (btw please ping me earlier next time, I don't get a notification if you reply here without mentioning me :)). I played with it and it looks good! The only thing that would need to be changed now is that Martin has merged his work to add chart_config entries for Mdim views and they would also need to be stripped of the defaults for completeness. I think it shouldn't be much work and it would be good to include this in this PR but if you think this is too much work now then it's also fine to merge this as is and do the mdim work in cooldown. |
Thanks! Yes, I'll rebase & update the PR |
3c89b72
to
fc31b87
Compare
@danyx23, as far as I can see, the defaults haven't been merged into the mdim view configs. Am I missing something? |
@sophiamersmann Ah interesting - that was sort of a bug in that work then that now is a feature :). Yes, then there is nothing left to do in that regard and this can go. |
Removes the default layer from the full config of charts.
This is the smaller version that removes the default layer from the full configs of all charts but keeps using it in the admin. If I find the time this week, I also want to remove the admin's dependence on the default config, but even if I don't find the time, I think this PR is okay to be merged as is since keeping the default config up-to-date is zero effort (we have a GitHub action that infers the default config from the schema and automatically commits it).
I tested this by comparing the previously baked Grapher configs with the now-baked Grapher configs. The diff was empty for most configs. There were a few that used to have
map.colorScale
set to an empty object (not sure why) that is missing now, but that makes no difference to Grapher.The SVG tester differences are due to a parent PR.