this leaves me with two options in this scenario (which i’ve come across) —

1. centralize the colorScheme observation and pass it down as an observable/binding to child views

2. cache the colorScheme in State

will try and find out which one is more suited to my project

thanks, this sounds amazing — i’ll check it out!

thanks, i’ve been posting on twitter/x but will now sharing updates here as well!

yeah i don’t use notion for collaboration at all, so i reckon obsidian would fit my use case as well

i always thought it looked really cool, but i’m too deeply rooted into notion at this point

worth switching?

not a game dev, but i’m working on my first ever side project — an iOS app