📓 3.4.0.5 Help Queue: Preparing for Firebase

We've now learned useEffect for running side effects, as well as the pattern for building custom hooks. Now let's look at the Help Queue and plan exactly how we'll use these tools to connect the app to Firebase.

Opening Your Project

Go ahead and open your Help Queue project from React Fundamentals.

As you read through this lesson as part of your weekend homework, you are not required to code along. The first classwork of the course section will prompt you to work through these lessons with your application.

Reviewing TicketControl

TicketControl is the component we'll be modifying the most. Here's an overview of its structure at the end of React Fundamentals:

src/components/TicketControl.js

function TicketControl() {
  const [mainTicketList, setMainTicketList] = useState([]);
  const [formVisibleOnPage, setFormVisibleOnPage] = useState(false);
  const [selectedTicket, setSelectedTicket] = useState(null);
  const [editing, setEditing] = useState(false);

  const handleClick = () => { ... }
  const handleDeletingTicket = (id) => { ... }
  const handleEditClick = () => { ... }
  const handleEditingTicketInList = (ticketToEdit) => { ... }
  const handleAddingNewTicketToList = (newTicket) => { ... }
  const handleChangingSelectedTicket = (id) => { ... }

  // conditional rendering ...
}

Right now, mainTicketList is a local array stored in memory. When the page refreshes, it resets to [].

What Will Change

Adding Firebase will change how tickets are stored and retrieved — but it won't change the shape of the app. Here's what will stay exactly the same:

• The component tree (App, Header, TicketControl, TicketList, Ticket, TicketDetail, NewTicketForm, EditTicketForm, ReusableForm)
• Props and callback functions
• Conditional rendering logic in TicketControl
• The formVisibleOnPage, selectedTicket, and editing state variables
• PropTypes on all components

Here's what will change:

• mainTicketList will be populated from Firestore instead of a local array

• A useEffect hook will subscribe to the Firestore tickets collection when TicketControl first mounts, so the component stays in sync with the database automatically:

  useEffect(() => {
    // subscribe to Firestore — when tickets change, call setMainTicketList with the new data
  }, []);

• The handler functions (handleAddingNewTicketToList, handleDeletingTicket, handleEditingTicketInList) will write to Firestore instead of updating local state directly. The remaining handlers manage UI state only and will stay the same.

What's Next

Before we can write any of this code, we need to understand Firebase and create a project. The upcoming lessons will cover:

1. What Firebase is and why we're using it
2. What NoSQL databases are and how they differ from SQL
3. Setting up a Firebase project and Firestore database
4. Connecting Firebase to our React app and writing our first database calls