expanding on #2051
With the feature flag enabled, we still lead to a blank page in /events as added in #2050 . Let's make it so that SCEvents actually renders the events displayed in SCEvents. This means Clark will need to grab the events from SCEvents, and THEN display them...
To do this, we'll need to:
- Ensure both Clark + SCEvents is running
- To make testing easier, create an event in SCEvents locally (use Postman or something... and then validate it exists by validating the response from the server's
/events endpoint)
- Add logic (probably a
useEffect) in SCEvents to fetch the events from SCEvents --> /events endpoint...
- Display all of the events in some sort of JSX --> again... this should be only returned if our feature flag is on
Regardless, we need to ensure that all SCEvents-related things will NOT be displayed publicly... this is done through the aforementioned feature gate, but make sure any data fetching added onto the new components do not run unless the feature flag is on...
this PR should make it so that locally running Clark can communicate with a locally running SCEvents
expanding on #2051
With the feature flag enabled, we still lead to a blank page in
/eventsas added in #2050 . Let's make it so that SCEvents actually renders the events displayed in SCEvents. This means Clark will need to grab the events from SCEvents, and THEN display them...To do this, we'll need to:
/eventsendpoint)useEffect) in SCEvents to fetch the events from SCEvents -->/eventsendpoint...Regardless, we need to ensure that all SCEvents-related things will NOT be displayed publicly... this is done through the aforementioned feature gate, but make sure any data fetching added onto the new components do not run unless the feature flag is on...
this PR should make it so that locally running Clark can communicate with a locally running SCEvents