Overview

API requests are being sent before authentication checks complete.

This is important for two reasons:

• We don't want to show data to users who shouldn't see it.
• We want the correct data to load for each user. The auth check returns info about the user which determines what shows up on the page.

This is probably because the RTK query hooks used in components to make API requests are fired as soon as they are mounted. Rather than trying to tell each component to wait until auth, we should probably make it so these components don't mount until the auth check completes. Implementing this could also resolve #78.

Expected Behavior

API requests should be sent after auth checks.

Actual Behavior

API requests happen are being sent before auth checks.

Steps to Reproduce

Note: These steps assume #148 has been merged.

• Login as a c1@example.com
• Go to the submissions page
• Open the network tab
• Refresh the page from the browser
• Notice the request to /api/boundaries with no query parameters
• Select a different utility
• Notice the request to /api/boundaries/?utilities=<selected utility id>
• Select the original utility
• Notice the request to api/boundaries/?utilities=<original utility id>

Demo