Jonathan Ochmann

By extracting the entire component css Stylesheet we're sacrificing the lazy loading aspect of components and are optimistically adding the entire css at page load. Maybe we should not attach...

Priority for this should be pretty low because the lazy component instantiation mechanism in sekoia already makes our 1000+ components apps super responsive.

I've since written a Gulp task that extracts the style property from components and adds it into a separate style sheet: ```javascript function extractCSS(stream) { const DEFINE_COMPONENT_REGEX = new RegExp('(defineComponent|createComponent|\\.extend)\\(\'(.|[\\n\\r])+?}\\)',...

Store rewritten to be non-persistent by default since Cue.js Beta version 1.03

Async handling implemented in 1.04 beta. Keeping this open b/c I'm undecided if this is the way to go and probably will be until I've written more example components

Fast forward to 2022 and I eventually settled on a hybrid approach were all state read/write ops are synchronous and observer resolution is asynchronous.

Implemented in 1.04-beta

closing. this was fixed a long time ago

Fixed in Cue.js Beta Version 1.03

Instead, we now return an HTML-String factory function that accepts an object of {attribute: value} pairs. The function adds the attributes into the HTML string and returns the hydrated HTML...