-
Notifications
You must be signed in to change notification settings - Fork 90
refactor(home-manager/firefox): factor out options into submodules #670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
different-name
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise LGTM, haven't had the chance to test it yet
| mkFirefoxModule = | ||
| args: | ||
|
|
||
| lib.modules.importApply ./mkFirefoxModule.nix ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the reason for separating this out into a new file so that it could be imported & used elsewhere? (even if it's external)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's more so to just keep each file simple
It felt kinda weird having such a massive function, and practically two cases of setting config. This is as opposed to now where mkFirefoxModule is written mostly just like a regular module, and the generation magic happens in this default.nix
Along with separating our `mkFirefoxModule` function, this should help cleanup the module as whole, while also making it much more understandable
cdebf87 to
b141cde
Compare
different-name
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
haven't tested this, but looks good to me! thank you again getchoo!
Along with separating our
mkFirefoxModulefunction, this should helpcleanup the module as whole, while also making it much more
understandable
CC @different-name