static-web-apps VS bulletproof-react

Latest issue: https://github.com/Azure/static-web-apps/issues/1404

FYI for 6. it usually means you have to set the fallback page to index.html on your host. Here's an azure static web apps issue referring to that problem https://github.com/Azure/static-web-apps/issues/702.

If you're using Azure Static Web Apps, you're likely to have this problem. Azure Static Web Apps doesn't support deep linking with authentication. When you get redirected you'll find you are (at best) missing the query parameters. If you take a look at the link here you'll see a suggested workaround. We're going to develop that idea in this post.

There is a limitation that affects authorization when you have a linked backend paired with an Azure Static Web App. Let's take the case of having an Azure Function App as the linked backend. Essentially the Azure Function app does not receive the claims that the Static Web App receives. There's an issue tracking this on GitHub, and it seems that this is a general problem with Static Web Apps, Azure AD and linked backends.

More information can be found in this GitHub issue. The workaround is based on this comment in a related pull request.

NOTE: Currently, you can't add configuration settings on a SWA that doesn't have any functions in it, so I also included a dummy HTTP function to allow configuration in production. I believe that it should be a valid scenario to only have proxies on your backend function app, so I created an issue on the Static Web App's GitHub repository. I'll update this post with any info they provide me.

Using -> this guide to help structure a project in a better way

bulletproof react

Well I’d definitely have a file structure in place. I use bullet proof react as my go to. But I mean like…I’d say there’s probably 10 things causing 90% of the problems. So things like folder structure, yes, but also how long the files are, I mean…how enmeshed it all is…maybe the naming conventions.

Follow this: https://github.com/alan2207/bulletproof-react

Your approach is similar to bulletproof-react, which I personally love. I have built projects of all sizes with it and the DX was always nice! Check it out if you want and good luck on your project 😁

Link for the lazy ones.

Not sure if this helps, but Bulletproof React is a very good architecture to React projects of any size. Maybe it can give you some insight on how to structure your project. Good luck!

Been content with how Bulletproof react does it, only thing missing for me is differentiation between views and components.