NullVoxPopuli

> with latest being returned twice, though: this is as optimized as it can be :tada: (and found out the two values :muscle: ) > Is there any good practice...

the pattern you describe is specific, and makes sense that you're running in to a bit of a rough edge with some primitives. "Keeping latest" is what I've called what...

Multi-file editing? https://www.sveltelab.dev/ This uses full web-containers which requires installing dependencies :thinking: Might be good to fork for ember later on

> To avoid this vivious cycle we must initialize contextual services **after** the transition is completed. do we want to do that? it means we can't access query params until...

Sorry it's been so long > URL as dynamic segment will not work. Kinda depends on how we want them to work, we _can_ make them work with a different...

I have this implemented in emberclear: - [service](https://github.com/NullVoxPopuli/emberclear/blob/master/client/web/emberclear/app/services/prism-manager.ts#L70-L77) - [build config](https://github.com/NullVoxPopuli/emberclear/blob/master/client/web/emberclear/config/build/static.js#L11-L14) what are thoughts on this approach? the downside is that it copies all prism assets into your dist directory...

what's the advantage of keeping additional files out of dist?

This issue isn't for humans to _do_ anything. :p It's a dashboard for humans with write access to the repo to override some renovate behaviors

I don't think this is something you'd want to _not_ use the real implementation for. Can you describe more what you're trying to do?

Yeah, the rule needs updating. The role is required here