Vuepress samples config stays in memory

[LeeLenaleee]

Documentation Is:

• Confusing

Please Explain in Detail...

With the new vuepress samples, options set with the actions it keeps that in memory for the other charts even though its not in there config which may be confusing,

If you go to: https://www.chartjs.org/docs/master/samples/legend/position.html and place the legend in the bottom and go to an chart where the tooltip location is not specified you will see it apear in the bottom as well like here: https://www.chartjs.org/docs/master/samples/title/alignment.html

Your Proposal for Changes

Only solution I can think of at the moment is to give every chart the default config of things we adjust like legend placement, tooltip placement and mode

[etimberg]

@simonbrunel have you seen this before with the editor plugin? My thought is that it's keeping the state and doing updates on page transitions rather than making a new chart.

[LeeLenaleee]

Some extra findings, if you for example take the legend postion and use the button to put it to the right it goes to the right, if you then write the options object to put it to the left it shows left, if you then go to another chart its on the right again so it looks like it keeps the state from the button update only and not from the editing field

[simonbrunel]

@etimberg I haven't but if I put a breakpoint right after chart.options.plugins.legend.position = 'right'; for the Position: right action and read Chart.defaults.plugins.legend.position, I get 'right'. I don't think it's caused by the editor component but it makes sense that charts on other pages are impacted since the Chart.defaults have changed.

[etimberg]

Hmmm, I don't know why that would be updating defaults. It should just be changing the local options.

[kurkle]

oh right. this is a proxy thing. it writes to the top level scope, which in this case is the defaults.

[etimberg]

Is there anyway to configure that? Seems like it should write to the lowest level scope