TL;DR: Struggling to keep form validation and UI in sync in your React app? Hereโs how I used Zod and React Hook Form together to define a single source of truthโdriving both runtime validation and required field indicators in the UI. The Problem: When Validation Drifts from UI Iโve been writing forms for as long as Iโve been writing codeโand …
So, you want to develop a new website with spiffy apps on Android and iOS, and you want that website and your APIs to run in Node Express. It sounds like a lot of work to write the website in React (or Flutter or whatever the language de jour is), the Android app with Android Studio, and the iOS app with Xcode…
Iโm currently working on several cloud-native projects hosted on Google Cloud Platform (GCP) that use .NET for the API and React for the UI. These projects rely on GCPโs Identity-Aware Proxy (IAP) to handle authentication, which occurs before any requests reach the Application Load Balancer or the application itself.
While GCPโs IAP offers robust security benefits, configuring a .NET and React application to work seamlessly with itโboth locally during development and when deployed to a Cloud Run instance as a Docker containerโproved to be more challenging than I expected. The available documentation and resources for this setup are sparse and often fragmented, making it difficult to piece together a clear solution.
This blog post is my way of sharing the lessons Iโve learned along the way. By outlining the steps and solutions that worked for me, I hope to save others from the trial and error I experienced and provide a clearer path for integrating GCP IAP with .NET and React applications.
In today’s fast-paced web development world, Next.js is one framework that’s becoming popular among developers. Itโs a powerful React-based solution that offers a lot more than just a traditional React and Node.js setup. What makes it so great? Letโs take a closer look.
Itโs time to release your latest front-end changes to production. However, as you create a new tag, you notice a large number of commits unrelated to the feature youโve been working on. Now, instead of simply kicking off your deployment and watching the pipeline run, you need to check with numerous developers and managers to ensure you donโt deploy any …