← Back to context Comment by LoganDark 10 days ago Pretty sure it used to be more server rendered? 2 comments LoganDark Reply princevegeta89 10 days ago Most of it still is server rendered. arp242 10 days ago I believe most stuff gets loaded via a JSON API now, and HTML rendered in JS via Rect. Maybe even all of it?For example the file overview has 14(!) requests (/recently-touched-branches, /latest-commit, /overview-files/{branch}, etc.).The issues list uses 5(!) requests to the GraphQL API. Didn't look in to why it needs five requests.
princevegeta89 10 days ago Most of it still is server rendered. arp242 10 days ago I believe most stuff gets loaded via a JSON API now, and HTML rendered in JS via Rect. Maybe even all of it?For example the file overview has 14(!) requests (/recently-touched-branches, /latest-commit, /overview-files/{branch}, etc.).The issues list uses 5(!) requests to the GraphQL API. Didn't look in to why it needs five requests.
arp242 10 days ago I believe most stuff gets loaded via a JSON API now, and HTML rendered in JS via Rect. Maybe even all of it?For example the file overview has 14(!) requests (/recently-touched-branches, /latest-commit, /overview-files/{branch}, etc.).The issues list uses 5(!) requests to the GraphQL API. Didn't look in to why it needs five requests.
Most of it still is server rendered.
I believe most stuff gets loaded via a JSON API now, and HTML rendered in JS via Rect. Maybe even all of it?
For example the file overview has 14(!) requests (/recently-touched-branches, /latest-commit, /overview-files/{branch}, etc.).
The issues list uses 5(!) requests to the GraphQL API. Didn't look in to why it needs five requests.