It would be actually interesting to see this clean architecture shown in a monorepo where the clean parts reside in a library and are re-used by two different frameworks, i.e. create-react-app and Angular.
Software engineer with a bachelor's degree in computer science focusing on clean code and clean architecture for web and mobile front-end applications. Currently in the master's degree.
This is something I'm always keen on. I hate it when libraries for what could be framework-agnostic tools are tightly coupled to the framework.
"If you want to fetch the price of milk install this library and call useMilkPrice()"
What if I want to fetch the price of milk outside of a react context.
This has also been a big annoyance when moving between frameworks. A library that could easily be applied to a vue application has to be abandoned because it's tightly coupled to react.
I always prefer a core library and then a framework-specific wrapper or adapter library.
Rant over.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It would be actually interesting to see this clean architecture shown in a monorepo where the clean parts reside in a library and are re-used by two different frameworks, i.e.
create-react-appandAngular.Very interesting point! It's already in my plans. hehe
Thank you for the contribution.
I agree and waiting.
This is something I'm always keen on. I hate it when libraries for what could be framework-agnostic tools are tightly coupled to the framework.
"If you want to fetch the price of milk install this library and call
useMilkPrice()"What if I want to fetch the price of milk outside of a react context.
This has also been a big annoyance when moving between frameworks. A library that could easily be applied to a vue application has to be abandoned because it's tightly coupled to react.
I always prefer a core library and then a framework-specific wrapper or adapter library.
Rant over.