Rich Text Versioning optimizations [MAPS-137] #10334
Open
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
FBanfi
approved these changes
Dec 15, 2025
| }); | ||
| return fetchedAssets.items; | ||
| } catch (error) { | ||
| console.error('Error fetching assets:', error); |
Collaborator
There was a problem hiding this comment.
💭 should we notify users? So they know that something went wrong. Also in the getEntries and the content type fetch?
Collaborator
Author
There was a problem hiding this comment.
We're already doing that 😎 In the createOptions function if we can't identify the entry, asset or content type we just display it as unknown. This just logs the specific error in the console to be able to debug
JuliRossi
approved these changes
Dec 16, 2025
Collaborator
JuliRossi
left a comment
JuliRossi
left a comment
There was a problem hiding this comment.
Looks good! Left some questions
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.
Purpose
A customer is having an issue in which the dialog of the app is not displaying correctly due to a "response too big" error.
Approach
We've introduced some optimizations so requests made by the app have a smaller response size:
createOptionsmethodselectparamester to only retrieve the title, which is the only thing that gets usedinclude: 0parameter when usingentry.getPublishedsince by default the response includes anincludearray that is not used