You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the homeManager module in a flake setup (import is the current master branch).
When I set scheme = "${inputs.tt-schemes}/base16/everforest.yaml"; the attrset produced by mkSchemeAttrs is structured in a way that it produces an error when using it with certain other nix modules like nixvims base16 colorscheme.
Am I missing an existing way to get a clean attrset (basically the output of yaml2attr) using the interface provided by config.scheme ?
Otherwise the value of config.scheme could be structured so one can easily access certain sets without other attributes like metadata.
I mean something like this:
Hi, thanks for the issue, I'm open to PRs if they won't break the compatibilty. Otherwise I don't have the time now to add more features. I think this is quite easy to implement in place in the config. IMO adding this as a separate attribute won't be of much benefit, I expect the discoverability of such helper stuff to be low.
I am using the homeManager module in a flake setup (import is the current master branch).
When I set
scheme = "${inputs.tt-schemes}/base16/everforest.yaml";
the attrset produced bymkSchemeAttrs
is structured in a way that it produces an error when using it with certain other nix modules like nixvims base16 colorscheme.Am I missing an existing way to get a clean attrset (basically the output of
yaml2attr
) using the interface provided byconfig.scheme
?Otherwise the value of
config.scheme
could be structured so one can easily access certain sets without other attributes like metadata.I mean something like this:
Can you advise on this?
The text was updated successfully, but these errors were encountered: