fix: dynamic node styling#104
Open
findthelorax wants to merge 6 commits intoPouzor:mainfrom
Open
Conversation
…ode true-false and will render container group node or base node
d44ae44 to
402eae4
Compare
Contributor
Author
|
Rebased onto latest main, resolved merge conflicts, and force-pushed the updated branch. |
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
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 is a larger PR fix for more consistent styling between nodes with the addition of multiple container nodes since not just proxmox can be a container node now.
Changes:
Removed the ProxmoxGroupNode.tsx and replaced it with ContainerGroupNode.tsx for clarity.
Created a DynamicNode.tsx file so nodes will render either with ContainerGroupNode styling if marked as a container node or as BaseNode styling if not.
Grouped nodeTypes.ts by type.