As anyone experienced with Rails production applications might know, there are times when certain features or parts of an application cause high memory usage and/or unacceptably slow response times.
We’re continuing our series on building a simple Software-As-A-Service (SaaS) application using React, Redux and Firebase. We’re utilizing Firebase as a Backend-As-A-Service (Baa), and building a simple application that demonstrates some of the core features.
We’ve been exporing different Backend-As-A-Service (BaaS) options and decided to publish a short series on how to build a simple Software-As-A-Service (SaaS) Application using React, Redux and Firebase.
While testing a feature that requires a confirmation, you may have seen a:
There are two different ways to accept the confirm alert in an acceptance/feature spec:
In the last post we wired up some of the UI with remote requests to our local api from our SPA section using React. In this post we’re going to continue fleshing out our CRUD features and wrap up the series.
This is Part 3 of our series on building a Rails 5.2 App with Webpacker and React. In the last post we organized our public and private systems to use different packs and assets, and prepared everything for developing the Dashboard.