Expose color palette as attributes #738
Open
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.
Expose a set of read-only attributes containing the chosen Catppuccin color palette.
Example usage:
This will help eliminate IFD for modules that require access to the color palette for various reasons. Users who wants to add personal touches/customizations to their themes will also benefit from this.
The workflow for the palette generation is meant to be run manually (via
workflow_dispatch), because I don't think it needs frequent/regular updates. But I can change that if necessary.I'm not confident with how the files are organized, but I've decided to create a separate file for the palette types because it got a bit long. Also, there might be a way to automatically generate the Nix types from the TypeScript types, but it's written manually by hand for now.
Fix: #734
Ref: #392