fix(react): Handle no-settings scenario
This commit is contained in:
parent
96ae664829
commit
743314062d
1 changed files with 1 additions and 1 deletions
|
@ -43,7 +43,7 @@ export const TestView = ({ Design, state, update, config }) => {
|
||||||
if (missingMeasurements(state)) return <Null />
|
if (missingMeasurements(state)) return <Null />
|
||||||
|
|
||||||
const { settings } = state
|
const { settings } = state
|
||||||
if (settings.sample) {
|
if (settings?.sample) {
|
||||||
/*
|
/*
|
||||||
* When testing/sampling one design, and then switching the editor to a different design,
|
* When testing/sampling one design, and then switching the editor to a different design,
|
||||||
* we run the risk that settings.sample holds invalid configuration. Like testing an unused
|
* we run the risk that settings.sample holds invalid configuration. Like testing an unused
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue