Feature: Client Cache for Document Type and Data Type Detail Models #19904
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
madsrasmussen
added
release/16.3.0
category/performance
madsrasmussen
changed the title
iOvergaard
approved these changes
Aug 18, 2025
Contributor
iOvergaard
left a comment
iOvergaard
left a comment
There was a problem hiding this comment.
Tested it out:
- Went to a document type to cache it
- Went back and forth and saw no new request ✅
- Opened it in another tab
- Changed a property
- Went back to it in the first tab
- Saw a new network request and the refreshed content ✅
This was referenced Oct 20, 2025
This was referenced Oct 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a client-side runtime cache to improve performance when loading Document Types and Data Types. This also includes Content Workspaces (Documents, Media, and Members), which all load structural data. The runtime cache means it will be cleared with a browser refresh.
When loading a Document Type or Data Type from the Management API, we cache the result to avoid re-requesting the server for the same data. The caching depends on a connection to the Server-Side Events hub for cache invalidation. If we don't have a connection, we won't cache anything.
The server events are emitted through a new
UMB_SERVER_EVENT_CONTEXTthat is made globally available. We can later use this when we introduce real-time updates in the UI.The PR also introduces a Management API Detail Request Manager that handles all the logic around when and if to cache the data. It is used within the server data sources, as it's the server data source that needs caching.
How to Test / What to Look For:
When loading a document, you will see network requests to load all the composed document types and data types. When loading another document based on the same document type, the number of network requests for Document Types and Data Types will no longer happen.