Is your feature request related to a problem? Please describe.
Currently, detection of the <SliceZone /> component (or its wrapper in case it only renders children like the one from @prismicio/react) is a bit hacky and could break/be inconsistent in some edge cases (e.g. users decide to render additional elements along the <SliceZone /> in its simulator).
Describe the solution you'd like
To deal with edge-cases, users could have the ability flag the <SliceZone /> component (or its wrapper) with a class (.slice-simulator-slicezone or (strict, TBD) a data attribute (data-slicezone). This flag would then be preferred when resolving the <SliceZone /> component or its wrapper.
Describe alternatives you've considered
The simulator could take care of rendering this <SliceZone /> component itself. However this limits the ability of users to wrap their <SliceZone /> component with containers or similar, like they might be doing in their applications.
Is your feature request related to a problem? Please describe.
Currently, detection of the
<SliceZone />component (or its wrapper in case it only renders children like the one from@prismicio/react) is a bit hacky and could break/be inconsistent in some edge cases (e.g. users decide to render additional elements along the<SliceZone />in its simulator).Describe the solution you'd like
To deal with edge-cases, users could have the ability flag the
<SliceZone />component (or its wrapper) with a class (.slice-simulator-slicezoneor (strict, TBD) a data attribute (data-slicezone). This flag would then be preferred when resolving the<SliceZone />component or its wrapper.Describe alternatives you've considered
The simulator could take care of rendering this
<SliceZone />component itself. However this limits the ability of users to wrap their<SliceZone />component with containers or similar, like they might be doing in their applications.Additional context
/