Mode in config seems to be ignored about matugen

[marcelohdez]

My hunch after a quick glance is that we generate colors in this function:

matugen/src/util/template.rs

Line 169 in d2a268b

let colors: Colors = generate_colors(schemes, source_color, default_scheme)?;

Which uses default_scheme which is only generated by the args in main.rs:

matugen/src/main.rs

Lines 68 to 70 in d2a268b

	let default_scheme = args
	.mode
	.expect("Something went wrong while parsing the mode");

But, we never read each template's mode when creating them, only the same colors variable as above:

matugen/src/util/template.rs

Lines 226 to 238 in d2a268b

	let data = engine
	.template(name)
	.render(upon::value! { colors: &colors, image: image, custom: &custom, })
	.to_string()
	.map_err(|error| {
	let message = format!(
	"[{} - {}]\n{:#}",
	name,
	input_path_absolute.display(),
	error
	);
	Report::new(error).wrap_err(message)
	})?;

(But I may be dumb, let me know if I am doing something incorrectly)

[InioX]

Hi @marcelohdez! Sorry for the very delayed response.

If you want the color to be always dark, you can specify the mode inside the keyword like this:

{{colors.<keyword>.dark.<format>}}

As for not reading the mode from the template, I rewrote the template code a while ago and completely forgot about it. Implementing it back would require to generate the colors for every template inside the loop and I think specifying the mode inside the keyword is enough. I will rewrite the documentation and remove the mode from config.