fix: border thickness hidden when setting border color from color picker

[Nithishvb]

Description

This PR fixes the issue where selecting a border color from the color picker causes the border thickness to be hidden. Now, the border thickness remains visible and correctly applied after choosing a color

Related Issues

#1804

Type of Change

• Bug fix
• New feature
• Documentation update
• Release
• Refactor
• Other (please describe):

Testing

Screenshots (if applicable)

Additional Notes

---

Important

Fixes issue in ColorInput where selecting a border color hid the border thickness by adjusting onValueChange callback.

• Bug Fix:
  • Fixes issue in ColorInput component where selecting a border color from the color picker hid the border thickness.
  • Changes onValueChange callback to use newValue.lightColor instead of colorValue in index.tsx.

^{This description was created by for 2dae37b. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 2dae37b in 34 seconds. Click for details.

• Reviewed 13 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. apps/studio/src/routes/editor/EditPanel/StylesTab/single/ColorInput/index.tsx:132

• Draft comment:
  Ensure newValue.lightColor is always the intended color for the border update. This change bypasses the computed colorValue, so verify that newValue.lightColor consistently preserves the correct border thickness styling.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to verify that a specific change is intentional and that it maintains the correct styling. It is not making a specific code suggestion or asking for a test to be written. It seems to be asking for confirmation of intention, which is against the rules.

2. apps/studio/src/routes/editor/EditPanel/StylesTab/single/ColorInput/index.tsx:132

• Draft comment:
  Using newValue.lightColor instead of the derived colorValue should fix the border display issue. Please ensure that newValue.lightColor is always defined in the expected format to avoid potential inconsistencies in components relying on onValueChange.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 50% <= threshold 50% The comment suggests a specific code change to fix an issue, which is useful. However, it also asks the author to ensure that a value is always defined in a certain format, which violates the rule against asking the author to ensure behavior. The first part of the comment is useful, but the second part is not.

3. apps/studio/src/routes/editor/EditPanel/StylesTab/single/ColorInput/index.tsx:4

• Draft comment:
  There's a potential typographical error in the import path: 'ColorPalletGroup'. Consider verifying if it should be 'ColorPaletteGroup' to maintain consistent naming.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_feoa10nS7GF4rs3L

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[Kitenite]

Great catch, thanks for the fix @Nithishvb!