Hi Team :wave: Thanks for the recent multi-level c...
# feature-requests
s
Hi Team šŸ‘‹ Thanks for the recent multi-level color palette update (Paint your charts your way) šŸŽ‰ It's a great update — really appreciate it! Building on that, I have a feature request regarding the color palette creation/editing UI. Apologies if this has already been requested before. Current pain point: Each color must be entered one-by-one into individual input fields. With up to 20 colors per palette and separate Light/Dark Mode configurations, creating and maintaining palettes is very time-consuming. Features that would be nice to have: • Bulk paste: paste a list of hex codes to fill all slots at once • File import: import palettes from JSON/YAML or common formats • YAML-based management in the project repo: define palettes as code, so changes can be version-controlled, reviewed via PR, and reused across environments (stg/prod) — consistent with the existing "Lightdash as code" approach (dbt metadata, CLI deploys) • *Copy Light Mode → Dark Mode*(and vice versa) with one click • *Duplicate an existing palette*as a starting point These would also pair really well with LLMs like Claude or ChatGPT: users could ask the LLM to generate a palette (e.g. "an accessible 10-color palette with both light and dark mode variants") and paste/import the result directly into Lightdash — instead of copying 40 hex codes by hand. YAML-based management would make this even smoother by letting the LLM produce a complete palette file ready to commit. Even just the bulk-paste option would dramatically improve day-to-day editing. Would you consider looking into this? šŸ™
āœ… 1
p
šŸ‘‹ Thanks for your message - someone from the Lightdash support team will get back to you asap. Feel free to add any additional context to the thread here in the meantime (screenshots, app version if you're self-hosting etc.).
o
Hey šŸ‘‹ Thanks for this suggestion! We've had a few options come through here. One other person asked for an API endpoint for these, do you think that would solve your problem? I imagine asking claude just to hit the API to update things in this case. I also like the concept of being yml based though!
šŸ‘€ 1
c
I've upvoted these issues for you: šŸ› ļø issue #23198 - this issue has been requested by 1 other user. šŸ› ļø issue #17155 - this issue has been requested by 1 other user. šŸ› ļø issue #13588 - this issue has been requested by 1 other user. I'll notify everyone here as soon as any of these issues are fixed.
s
@Oliver Ramsay Thanks for creating and sharing the issues! šŸ™ Ah, I didn't realize palettes could be edited via the API — I'll check it out and give it a try!
hi @Oliver Ramsay I tried the API with a PAT (together with Claude). GET /api/v1/org/color-palettes works fine, but POST and PATCH return 401 AuthorizationError.😭 I had Claude check the source, and it pointed out that in organizationController.ts the GET uses
[allowApiKeyAuthentication, isAuthenticated]
, while the mutation endpoints use
[isAuthenticated, unauthorisedInDemo]
. Claude's interpretation is that this is why PAT auth doesn't work for writes.šŸ¤”
p
Ah, the API is currently not live right now, sorry for the confusion! It's just that someone else asked for it and it should be live soon!
Here's the github issue, which I will link to this thread, once it's fixed you'll get updated here automatically. I'm expecting that will be over the next few days. https://github.com/lightdash/lightdash/issues/23194
šŸ‘Œ 1
c
I've upvoted issue #23194 for you! This issue has been requested by 2 other users. I'll notify everyone here as soon as it's fixed.
āœ… We've fixed issue #23194: Color palette write endpoints missing allowApiKeyAuthentication middleware Lightdash Cloud users will automatically get the fix once your instance updates (All instances update at 01:00 PST [10:00 CET] daily). Self-hosted users should update to the latest version to get the fix šŸŽ‰