You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This request is partially for debugging/development purposes, partially for style isolation without a shadowdom (which removes all styles of the parent context).
For this change to be uniformly implemented, the inline-demos in markdown files would need to be extracted to components during build time, rather than line-by-line inlined in the hbs output. This would allow passing a dynamic-segment to some route for dynamically loading the component for the above development scenario. With embroider+vite, this would also lead to much faster rebuild times, as all the surrounding UI wouldn't need to be built/rendered.
I think at build time, an object like this would need to be generated:
This request is partially for debugging/development purposes, partially for style isolation without a shadowdom (which removes all styles of the parent context).
For this change to be uniformly implemented, the inline-demos in markdown files would need to be extracted to components during build time, rather than line-by-line inlined in the hbs output. This would allow passing a dynamic-segment to some route for dynamically loading the component for the above development scenario. With embroider+vite, this would also lead to much faster rebuild times, as all the surrounding UI wouldn't need to be built/rendered.
I think at build time, an object like this would need to be generated:
The text was updated successfully, but these errors were encountered: