csslint VS MobX

CSS Lint

With that being said, you could run some css linter I believe if you really decided to let them to do. Maybe leverage something like this: https://github.com/CSSLint/csslint

http://csslint.net/ ?

Thanks in advance folks, if anyone would like to see any info or pics or whatever, I can post. If I haven't gone mad or blind from going thru too many lines of code. (it's hard to use things like CSSLint because of all the !importants you have to use to supercede stuff, and csslint.net flags every --variable-name as an error, so even after switching off everything but basic checking it doesnt work too well, not catching simple syntax errors even... maybe I should look into something better there)

VSCode can do real-time linting for you, or you can run it through an online linter.

Sorry, meant http://csslint.net - edited to change.

Second, check to make sure you didn't make a change to your CSS which broke all of the CSS after that point. You could use a site like CSS Lint to help check that for you (just copy-and-paste all of your CSS there and click "Lint").

You can use a linting site, such as http://csslint.net/, to check for syntax & redundancy errors before you save them to your sub's stylesheet.

Also you could look into linting your css (http://csslint.net/) This will force consistency in the way you write and catch mistakes

You might want to run your CSS code through a CSS error checker, like CSS Lint, to help you find errors like that. (Note: It's very picky, so you may get lots of warnings that you may be able to ignore, but you should definitely fix any errors.)

States can also be organized in some central places (aka. stores). You can use Tini Store (very simple, ~50 lines) or other state management solutions such as MobX, TinyX, ...

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

MobX

Mutable-based: leverages proxy to create mutable data sources which can be directly written to or reactively read from. Candidates in this group are MobX and Valtio.

Looks good! FWIW I always felt the observable pattern much more intuitive than the redux/reducer style. Something like https://mobx.js.org/

Things get hairy in both, but redux pattern feels so ridiculously ceremonially to effectively manage a huge global state object with a false sense of "purity".

Observables otoh say "fuck it, I'm mutating everything, do what you want with it".

MobX Documentation

There's also others libraries like https://github.com/mobxjs/mobx which aren't specific to RN but can be used in any JS environment.

Valtio is like simplified MobX

Link: https://mobx.js.org