-
CustomHookSample
Sample code for the dev.to blog post: Simplify Using Hooks by Using Custom Hooks in React
View on GitHub
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
After working with AngularJS for a little while, a colleague recommended React, and then after trying (and failing with) Redux, I embraced hooks and naturally function components in React. While my back end APIs are still all written in .NET Core, and now that .NET Core has become .NET 6, I don't even run my front-end SPAs in ASP.NET any more. They are now static web pages created as React projects with npm hosted in Azure static web apps with the back ends in either App Services or Function Services depending on the level of authorization that is needed (e.g. simple client app auth or policy based auth). Oh, and did I mention the data is typically in either Azure Managed SQL or Azure Storage?
-
I do a lot of enterprise application development in a very small team. It's important for us to create applications that work on any device with a modern web browser that is connected to the Internet and not just a LAN or VPN. The apps must authenticate thru single-sign on that is federated with the company Active Directory. The apps need to rely on commonly available libraries like React and Bootstrap albeit through ReactStrap, and they must be spartan and similar. That is to say that users need to be able log onto all of the various apps the same way, and the apps need to do simply what they need to do with no bells or whistles. Furthermore, one app should look and feel like the others. We don't want to confuse users by making them feel like they need to learn a whole new system for every new application.
-
After working with AngularJS for a little while, a colleague recommended React, and then after trying (and failing with) Redux, I embraced hooks and naturally function components in React. While my back end APIs are still all written in .NET Core, and now that .NET Core has become .NET 6, I don't even run my front-end SPAs in ASP.NET any more. They are now static web pages created as React projects with npm hosted in Azure static web apps with the back ends in either App Services or Function Services depending on the level of authorization that is needed (e.g. simple client app auth or policy based auth). Oh, and did I mention the data is typically in either Azure Managed SQL or Azure Storage?
-
The Alert element from ReactStrap is a good start, but it only handles a border and colors. If you want something more than text, you're going to have to find some other elements to add. How about the circle-check icon from FontAwesome. So now we have icons, colors, and text to keep track of. I gave it some thought and realized that given the standard Bootstrap colors, commonly available and understood icons, and most importantly the kinds of things that can happen with CRUD-type applications we can come up with a very limited list of combinations that can be used in the vast majority of cases when managing operations in our application, particularly those that might take a significant amount of time. After all, we don't want to leave our users hanging.
-
After working with AngularJS for a little while, a colleague recommended React, and then after trying (and failing with) Redux, I embraced hooks and naturally function components in React. While my back end APIs are still all written in .NET Core, and now that .NET Core has become .NET 6, I don't even run my front-end SPAs in ASP.NET any more. They are now static web pages created as React projects with npm hosted in Azure static web apps with the back ends in either App Services or Function Services depending on the level of authorization that is needed (e.g. simple client app auth or policy based auth). Oh, and did I mention the data is typically in either Azure Managed SQL or Azure Storage?
-
After working with AngularJS for a little while, a colleague recommended React, and then after trying (and failing with) Redux, I embraced hooks and naturally function components in React. While my back end APIs are still all written in .NET Core, and now that .NET Core has become .NET 6, I don't even run my front-end SPAs in ASP.NET any more. They are now static web pages created as React projects with npm hosted in Azure static web apps with the back ends in either App Services or Function Services depending on the level of authorization that is needed (e.g. simple client app auth or policy based auth). Oh, and did I mention the data is typically in either Azure Managed SQL or Azure Storage?
