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 agree, It would be good to enforce that convention. The main thing that has been holding me back is about what to do with the overlay function signature.
Let's say we have a wrapper like this:
name: overlay:
# The wrapping overlayfinal: prev: {"${name}"=importoverlayfinalprev;}
Where name is the name of the flake, and overlay the location of the user overlay.
In that case, the user overlay can not use final to access its own attributes.
Here the user has to know the name of the flake to access one.
We could recommend to use the rec keyword, but then the flake becomes un-overridable because it's bound to the local scope.
So the only option is to add a third argument and change the function signature. It also means that the overlay becomes unusable outside of flake-utils without a similar wrapper.
I can faintly see why package overlays are namespaced, even though simple flake does not reexport them in
output.overlay
.Is it enough to encourage this as a convention vs enforcing it in the flake spec?
The text was updated successfully, but these errors were encountered: