Render event sources asynchronous, as they are fetched
See original GitHub issueOriginally reported on Google Code with ID 1405
Currently, fetchEventSource method checks if all pending sources have their events normalized
before calling reportEvents, which will then clean the complete view.
Since multiple sources can be defined, it makes sense to normalize and display their
events asynchronously instead of waiting for all sources to be fully processed before
continuing. I think that source should not delay all other.
Reported by marco@zoqui.com
on 2012-05-15 12:17:27
Imported with 9 stars.
Issue Analytics
- State:
- Created 8 years ago
- Comments:15 (11 by maintainers)
Top Results From Across the Web
React Suspense: Async rendering in React - LogRocket Blog
This is a common method used to ensure good UX for apps that are fetching data from external sources. All you have to...
Read more >Update on Async Rendering – React Blog
The upcoming suspense APIs will make async data fetching cleanly possible for both client and server rendering.
Read more >Asynchronous Data Queries - Recoil
Asynchronous Data Queries. Recoil provides a way to map state and derived state to React components via a data-flow graph. What's really powerful...
Read more >How To Handle Async Data Loading, Lazy Loading, and Code ...
You'll load data using an asynchronous function that simulates a request to an external data source. First, create a component called ...
Read more >Handling Asynchronous fetching of data with React & Redux
Display a list of fetched cat names. · Display a message, icon, or in general a component when it is actually fetching data...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue has been addressed in the latest alpha release (4.0.0-alpha.2) See the blog post »
https://fullcalendar.io/docs/v4/progressiveEventRendering
V4 was officially released a few days ago!