Closed vxsl closed 2 years ago
@vxsl Will approve this, all the issues I raised here can be addressed in another PR, as well as anything @sallkall might want to have changed on design part. There are quite a few changes from both of us again on the common files for charts and map so I would really like to do a rebase of my branch before I add to the editor part for the map.
The overflow of the selection list in the DropdownSelect which makes the control panel to change height. I saw a PR with the component in lumen-labs, not sure you addressed this.
Thanks for pointing that out, fix included in the next PR
The flickering of the charts when loading and changing containers needs also to be fixed. In my opinion it makes for a very poor UX.
Agreed, will probably just remove this mechanism, as it was intended to make it less choppy by reducing viz re-renders, but the flashing is super annoying. Maybe if I have time in the future I will take another stab at a more graceful solution to this problem.
I believe dataHasVariance has to be set resettable: true in the state model
Good catch, will test and include in the next PR
Will approve this, all the issues I raised here can be addressed in another PR, as well as anything @sallkall might want to have changed on design part. There are quite a few changes from both of us again on the common files for charts and map so I would really like to do a rebase of my branch before I add to the editor part for the map.
Sounds good. Merging now.
question - is this going to be the MVP editor view or should I reframe from giving design comments until you have the full-page widget editor view up?
As discussed yesterday we can wait :+1:
should this action reside within the same hook right below it? since the dependencies are exactly the same and that one isn't very bloated yet
Yes absolutely, good catch
we should prefer elaborate if/else statements over ternary when there is a nested logic
True, this is a bad habit of mine - at some point will refactor this custom hook to apply this across each memo
if we're in the mood for regex all the way
nice, going to replace the fn in next PR
also we can consider using css to transform text to capital
Unfortunately can't, as this logic is independent of the rendering library
depends on EQWorks/chart-system#155
^ among generally implementing the below new features, EQWorks/chart-system#155 decouples subplot rendering, titles, and legends from
plotly.js
so we can have finer control. Thus, suggestions on how the legend should be styled, how the titles should be styled, etc are now welcome.viz-options
constants to facilitate new features described belowgenericOptions
)showLegend
has been moved from a specificoption
ofpie
to agenericOption
adapter
new features
grouping by value
https://user-images.githubusercontent.com/53827672/150403920-d016f387-2990-489c-b87d-d305b818dfe6.mp4
group filtering
https://user-images.githubusercontent.com/53827672/150404115-c319c251-5a81-456f-ae7d-a834c19a6a2e.mp4
subplot title positioning
https://user-images.githubusercontent.com/53827672/150404419-ca1cbc78-f00f-4306-924e-f6b4feb2f6f1.mp4
legend positioning
https://user-images.githubusercontent.com/53827672/150404563-087b9322-fe47-4664-bcca-72351b5d98d9.mp4
hue control
baseColor
is currently lacking as well. https://user-images.githubusercontent.com/53827672/150404955-d136a837-932c-4a40-b77e-1a4673d8157b.mp4size control
https://user-images.githubusercontent.com/53827672/150405409-db4204ef-bc65-4f5a-b7e0-01ddc0431009.mp4
size-limit
from 500KB to 600KBstories/sample-data.js
from thesize-limit
calculation but I couldn't get theignore
option to workplotly
, even using thebasic
subset of the library, discussed in EQWorks/chart-system#150