Open IgorShadurin opened 8 months ago
While exploring solutions to avoid Provider Wrapper Hell in our codebase, I came across an interesting approach detailed in an article (https://javascript.plainenglish.io/embrace-react-composition-for-cleaner-code-a-better-alternative-to-provider-wrapper-hell-ead75512091a). The article suggests embracing React composition as a cleaner and more efficient alternative.
I propose we consider integrating a similar solution. This could streamline our code, making it more maintainable and less cluttered with nested components.
https://github.com/fairDataSociety/fairdrive-theapp/blob/c3732aabfa2881d9e27fc785a0bb11c3f3ca9e64/src/pages/_app.tsx#L45
While exploring solutions to avoid Provider Wrapper Hell in our codebase, I came across an interesting approach detailed in an article (https://javascript.plainenglish.io/embrace-react-composition-for-cleaner-code-a-better-alternative-to-provider-wrapper-hell-ead75512091a). The article suggests embracing React composition as a cleaner and more efficient alternative.
I propose we consider integrating a similar solution. This could streamline our code, making it more maintainable and less cluttered with nested components.
https://github.com/fairDataSociety/fairdrive-theapp/blob/c3732aabfa2881d9e27fc785a0bb11c3f3ca9e64/src/pages/_app.tsx#L45