You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The request that fetches the shapes is not paginated and there is no lazy loading implemented. Hypothetically, if there were a large number of shapes created in the near future the page would load all of them immediately which could lead to requests with a large amount of data and a lot more waiting for users with bad internet.
Describe the solution you'd like
The solution would be making the requests on the backend paginated while on the frontend lazy loading can be implemented by using IntersectionObserver or something of the like.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The request that fetches the shapes is not paginated and there is no lazy loading implemented. Hypothetically, if there were a large number of shapes created in the near future the page would load all of them immediately which could lead to requests with a large amount of data and a lot more waiting for users with bad internet.
Describe the solution you'd like
The solution would be making the requests on the backend paginated while on the frontend lazy loading can be implemented by using
IntersectionObserver
or something of the like.The text was updated successfully, but these errors were encountered: