karlinator / butikk.gijernet.no Goto Github PK

Make use of, for instance, this component to lazy load images.

Low priority due to not that many images present. More important (and useful) for mobile.

Two instances of the Controls element is drawn, both in Browse and Product. These do not keep state between them.

Solution: move state to the parent element, pass events up and state down as props.

Right now, the products API method only supports a maximum of 100 products. This can be solved by 'paging' through the Stripe data (which caps at 100 products per request), checking the has_more attribute to do so.

It occurs to me that almost all the information required across the entire site is already sent out by default with the products function. Every product with every attribute. The only, and I mean only, thing missing is the descriptions.

It should be eminently possible to convert the site into a Progressive Web App (or just reduce server load in general) by making the products function return all the info by default, enable caching on it (google cdn and client side) and then simply storing it as global state in the app. This would eliminate all loading times and API calls except on initial load (which might still not require a full request, see caching and PWA) and on checkout calls.

Add more events, test that disabling "statistics" cookies actually prevents Analytics data and vice versa.

Some of the functions can make use of caching. In particular, the 'products' and 'productDetails' can be cached, with maybe up to a few days of TTL.

To do this, it needs to migrate back to a https based (and not onCall) function. This also means moving them back to us-central1, but this is, I think, a small price to pay for caching requests.

Warning: There is no way to 'clear cache' manually, this is controlled entirely by TTL. Cache time might need to be short so updates actually propagate. Consult with customer.