The relationship editor currently has to make several requests to /ws/js/type-info before it can load and display itself. While these requests are normally fast, our servers can be slow to respond when handling abnormal levels of traffic, leaving users waiting for 30s or more in exceptional cases (MBS-14194).

Reducing the number of network requests is a worthwhile goal in itself, so it likely makes sense to further cache this data on the client in IndexedDB. (We currently use ETags, which still requires a round-trip to the server.)