fix: [#9346] Remove new line symbol from LGWidget #9435
Closed
Conversation
This file contains 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
sw-joelmut
requested review from
cwhitten,
boydc2014,
a-b-r-o-w-n,
srinaath,
benbrown,
tdurnford,
natalgar and
VamsiModem
as code owners
|
Closed as it's no longer necessary |
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.
Addresses #9346
#minor
Description
This PR solves part of an issue when rendering the LGWidget component (internal process to recognize language generation texts) to the Authoring Canvas UI.
Language generation texts that have multiple lines, new lines are being replaced with the ↵ symbol concatenating the texts into a single one causing the memory to increase when interacting in Composer.
By removing the new line symbol, and just leave the text as is (with the new lines only) reduced the amount of memory storage used.
Specific Changes
Testing
The following image shows the before and after the applied fix, how the memory usage and the Authoring Canvas behaves.
