fix: 4178 - current generated message options should be visible #4196
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.
Describe Your Changes
This pull request aims to enhance the current generate message by ensuring that the message options are always visible at the bottom.
Previously, these options were absolute positioned, which meant that the parent visible frame was not measured accordingly. This fix will remove the absolute class when this is a currently generated message. Instead, it will use flex orders to swap out the components’ order accordingly.
Short thread
Long thread
Error message should not be capitalized like this:
But like this
Fixes Issues
Changes made
The code changes involve adjustments to the
ChatItem
andMessageContainer
components.In
ChatItem
:isCurrentMessage
prop to theMessageContainer
component, defaulting tofalse
if undefined.In
TextMessage
:MessageContainer
to include theisCurrentMessage
boolean prop.getCurrentChatMessagesAtom
import and its usage.These changes seem to enhance the message display logic and manage the CSS class application dynamically based on the message context.