Skip to content

ERA-9761: Add page_size to event feed requests #1123

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

luixlive
Copy link
Contributor

No description provided.

@luixlive luixlive requested review from gaboDev and JoshuaVulcan May 22, 2024 18:23
@luixlive luixlive requested a review from JoshuaVulcan May 24, 2024 18:39
@luixlive
Copy link
Contributor Author

@JoshuaVulcan this PR was updated with further changes with the same intention that the original change: ease the feed request. Now we are not including the event updates when fetching the feed, instead now everytime we open an event page we reload that event so we make sure we have all we need to show the page.

@@ -109,24 +110,24 @@ const ReportManager = ({ onReportBeingAdded }) => {
}, [isNewReport, location.pathname, location.search, location.state, navigate, newReportTemporalId, reportType]);

useEffect(() => {
if (!isNewReport && !eventStore[reportId]) {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We no longer check if the event is in the store, cause probably it is if it was loaded by the feed, but it won't have the updates property.

Copy link
Collaborator

@JoshuaVulcan JoshuaVulcan May 29, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't mind this, but it's a little blunt and takes away an (overall helpful) optimization. Clicking any previously-viewed event will cause duplicate requests. Could we eval with a function to test if the event's data structure is complete and only fetch if not?

formProps={navigationData?.formProps}
isNewReport={isNewReport}
key={reportId} // This resets component state when the id changes
newReportTypeId={newReportTypeId}
onAddReport={onAddReport}
reportData={reportData}
reportId={reportId}
/>}
/> : <LoadingOverlay />}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a loading spinner

@@ -29,7 +29,7 @@ const useReportsFeed = () => {
return isEqual(restEventFilter, INITIAL_FILTER_STATE);
}, [eventFilter]);
const eventParams = useRef(calcEventFilterForRequest(
{ params: { exclude_contained: shouldExcludeContained }, format: 'object' },
{ params: { exclude_contained: shouldExcludeContained, include_updates: false, page_size: 25 }, format: 'object' },
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We exclude the updates property from the feed request and make sure to only load 25 events

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

include_related_events, include_notes, include_details, and include_files are also available as parameters here. Should we slim this down even further?

@luixlive luixlive temporarily deployed to event-feed-page-size May 24, 2024 18:43 — with GitHub Actions Inactive
@luixlive luixlive changed the title Add page_size to event feed requests ERA-9761: Add page_size to event feed requests May 29, 2024
@luixlive luixlive temporarily deployed to event-feed-page-size May 30, 2024 15:58 — with GitHub Actions Inactive
@AlanCalvillo
Copy link
Contributor

After we create a brand new event. When we try to open it back, the load spinner in the event details gets clogged. It's interesting, though, bc no request in the Network is open and no console error is prompted.
image

@luixlive luixlive closed this Jun 5, 2024
@luixlive luixlive deleted the event-feed-page-size branch June 5, 2024 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants