fix: add code button decoration when throwing custom component in screen #6823
+79
−1
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
dosubot
bot
added
the
size:XS
dosubot
bot
added
size:M
github-actions
bot
added
bug
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 pull request includes changes to the
FlowPagecomponent and theflowStoreto improve the functionality and user experience. The most important changes include adding a memoized check for custom components and modifying the default selection state of new nodes.Improvements in
FlowPagecomponent:src/frontend/src/pages/FlowPage/components/nodeToolbarComponent/index.tsx: Added a memoized check to determine if a node is a custom component and applied a conditional class to the toolbar button.Enhancements in
flowStore:src/frontend/src/stores/flowStore.ts: Changed the default selection state of new nodes to be selected when added to the state.