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'm debugging my flake-parts code with nix repl. To do this, I put custom values into flake attribute.
However, sometimes I need values provided for perSystem lambda like lib, pkgs to debug more conveniently.
AFAIK, I can't add custom attributes inside perSystem without adding custom options. It would be great if I could add attributes for debugging purpose into perSystem. Do we have any?
The text was updated successfully, but these errors were encountered:
bglgwyng
changed the title
What is the best way to debug things inside perSystem?
What is the best way to custom attributes for debugging purpose inside perSystem?
Oct 31, 2024
The best solution I found so far is to put debug2 attribute manually in imports. debug is different from what I expected. Do we have such thing in default?
Using debug, I should define values for debugging purposes in REPL. Is it correct? #256 (comment)
This approach allows arbitrary properties inside perSystem.debug.
What about adding this feature into the existing debug option?
I'm debugging my flake-parts code with nix repl. To do this, I put custom values into
flake
attribute.However, sometimes I need values provided for
perSystem
lambda likelib
,pkgs
to debug more conveniently.AFAIK, I can't add custom attributes inside
perSystem
without adding custom options. It would be great if I could add attributes for debugging purpose intoperSystem
. Do we have any?The text was updated successfully, but these errors were encountered: