The following emojis: 🌻, 🪴, 🌺 and 🌿 are tied to Latte, Frappé, Macchiato and Mocha. It'd be nice to ship them as part of the palette.json so we can pull them into the language libraries and whiskers.

Mostly raising this because I've seen the following whiskers v2 code in dark-reader and github-readme-stats:

{% for id, flavor in flavors %}
<details>
{%- if id == "latte" %}
<summary>🌻 Latte</summary>
{%- elif id == "frappe" %}
<summary>🪴 Frappé</summary>
{%- elif id == "macchiato" %}
<summary>🌺 Macchiato</summary>
{%- else %}
<summary>🌿 Mocha</summary>
{%- endif %}
...

And it'd be nice to reduce that into:

{% for id, flavor in flavors %}
<details>
<summary>{{flavor.emoji}} {{flavor.name}}</summary>
...

I think the typing in the NPM package is pretty suboptimal currently, and also contains errors. (#34)
Also, not really sure about the labels export? In most cases, you would think of the color being part of a flavor, rather than first selecting the color, then the flavor...

Ideally, I'd like to use TS for a nice API with the JSON exports, and generate the JSON programmatically somehow.
We'd only really need 26 colors * 4 flavors, generate the other formats, then export them in the NPM package.

Currently working on this until I'm happy enough with it to raise a PR:
https://gist.github.com/nekowinston/98b363b45e7fbe3256c5ff84a1ed8b07

is a port for shadcn/svelte planned? uwu owo

This allows for directly iterating over the types with a for loop, rather than manually needing to call into_iter()
std::iter::IntoIterator trait documentation in the std library

Can be taken from Dracula's LibreOffice palette.
Ideally, it would have 4 separate palettes, for the 4 catppuccin palettes.

JavaScript is a great language but NPM has packaging issues at times, mostly with vulnerabilities. Python is another great language which doesn't have these issues. I will be willing to contribute to this to add Python support along with JavaScript support.

shows up as being defined but throws error when used

Motivation

I want to pattern match on the current flavour.

// Fix latte colours
if matches!(flavour, Latte) {
	...
}

Proposed solution

pub enum Flavour {
	Latte,
	...
}

impl Flavour {
	pub fn name(&self) -> &'static str { ... }

	pub fn palette(&self) -> Palette { ... }
	// OR
	pub fn rosewater(&self) -> Colour { ... }
	pub fn flamingo(&self) -> Colour { ... }
	pub fn pink(&self) -> Colour { ... }
	...
}

This would be used as such

Flavour::Latte.sky()

rather than the current way of

Flavour::Latte.palette().sky

Right now we use Palette to refer to colours of each flavours, which after some discussion in the Discord, we ended up with the conclusion that this is the wrong name, as palette usually is used to refer to all 4 flavours as a whole.

The new naming we ended up with is changing Palette to FlavourColours

Currently if someone needs to maintain for example the Rust crate, they have to be given access to the entire repo
This is obviously not an ideal situation. A solution to this would be to move each project out into a separate repo and then including them in this repo as a submodules, that way this repo just acts as a sort of hub.

This should probably just be done for future projects being added and perhaps the Rust crate as its still fairly new, as backporting this to the other projects in here, is a pain that probably isn't worth it.

I have a kotlin version of the library. Is it worth it make it official and make a proper readme?
https://github.com/lighttigerXIV/catppuccin-kt