Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Color Picker for Customer Cases #915

Merged
merged 2 commits into from
Nov 27, 2024
Merged

feat: Color Picker for Customer Cases #915

merged 2 commits into from
Nov 27, 2024

Conversation

trulshj
Copy link
Contributor

@trulshj trulshj commented Nov 27, 2024

A bit cursed, but this allows you to choose a subsection of the title to apply color to

TODO: Validation that the title actually contains the subsection you input

image

Fancy Color Picker Components!

Possible TODO: Show a preview of title / Badges

image

How these colors look applied:

image

Copy link

vercel bot commented Nov 27, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
variant-no ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 27, 2024 3:03pm
variant-se-2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 27, 2024 3:03pm

@@ -39,7 +39,34 @@ const customerCase = defineType({
type: "internationalizedArrayString",
title: "Title",
}),
defineField({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to the design the colors for the title and badge should be the same, is there any way to validate this or should we add that in the description?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or could we use one color picker for the "main" color, and another for the text? 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If they should always be the same, then we should only have one field for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants