Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Switching from one package to another should not persist options

See original GitHub issue

Category Plugins

Component dev-tools

Describe the bug While trying to look at the field-date I found that pulling up the test page does not display a toolbox with the field-date in it. I think this has to do with: createPlayground(document.getElementById('root'), createWorkspace, defaultOptions);

To Reproduce

Steps to reproduce the behavior:

Go to field date
run npm run start
Notice the toolbox is the default toolbox

Expected behavior A toolbox with the field-date.

Screenshots

Additional context

Issue Analytics

State:
Created 3 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

samelhusseinicommented, Sep 9, 2020

I think that makes a case for having project specific options. ie: some way to tell that you’ve moved from running the playground from field-slider to field-date, and I agree those two shouldn’t share options.

As for what options are project dependent, I think it depends on the plugin you’re building. eg: if you’re building a theme plugin, then the theme is going to be project dependent, and say perhaps you were building something that is RTL specific, then the rtl flag would be.

I think we can pass the current plugin name to the playground through the URL loaded, and have it save options under that domain.

0reactions

alschmiedtcommented, Sep 9, 2020

It seems to me that a toolbox is project dependent while most other options are not. When I run a different project I expect whatever toolbox that project is created with to be displayed. Having to hit reset in this case doesn’t seem very intuitive.