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
It's starting to look nice, but it's slow to load. There are ways we can make it quicker.
Break up the response
We could have the angular front end ask not for "all features" but instead "all features from this provider", followed by "all features from another" etc - so that the page appears in chunks. We'd still provide the option of asking for "all features" but just choose not to use it on our front end.
Pre fetch and store.
I think when it comes to viewing a feature and calculating differences between branches, we're going to need to be doing things more cleverly on the server.
One way would be to ask for more permission from the github user (for example) to auto set up a callback on commit hook. We can then recalculate every time we hear about a commit for a user, and the data will be sitting there when they hit the site.
We should also break up the feature view and have any planning info brought back separately to the source code stuff.
The text was updated successfully, but these errors were encountered:
I want this tool to be slick and quick.
It's starting to look nice, but it's slow to load. There are ways we can make it quicker.
Break up the response
We could have the angular front end ask not for "all features" but instead "all features from this provider", followed by "all features from another" etc - so that the page appears in chunks. We'd still provide the option of asking for "all features" but just choose not to use it on our front end.
Pre fetch and store.
I think when it comes to viewing a feature and calculating differences between branches, we're going to need to be doing things more cleverly on the server.
One way would be to ask for more permission from the github user (for example) to auto set up a callback on commit hook. We can then recalculate every time we hear about a commit for a user, and the data will be sitting there when they hit the site.
We should also break up the feature view and have any planning info brought back separately to the source code stuff.
The text was updated successfully, but these errors were encountered: