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
Haskell developers will always remain the primary audience of haskell-flake. For users who just want to package the Haskell app without needing the full-blown development environment, the following configuration is useful:
(These just disable the default build tools added by haskell-flake).
However, this configuration does not prevent the addition of devShell itself that is going to remain unused by these users.
From an API standpoint, how can we provide a simpler option to disable the whole development shell and friends for this target audience (non-Haskell developer users)?
The text was updated successfully, but these errors were encountered:
... should disable the devShell injection entirely, thus all of buildTools becomes unused. But since buildTools (EDIT: also the check options) now becomes contingent on this new development flag, perhaps we should move it under that as well, viz.:
haskellProjects.default={packages={};overrides=self: super: {};development={enable=true;# True by defaultbuildTools=hp: {ghcid=null;fourmolu=hp.fourmolu;};hlintCheck.enable=true;hlsCheck.enable=true;};
development = false can also disable the checks; leaving packages only.
Haskell developers will always remain the primary audience of
haskell-flake
. For users who just want to package the Haskell app without needing the full-blown development environment, the following configuration is useful:(These just disable the default build tools added by haskell-flake).
However, this configuration does not prevent the addition of
devShell
itself that is going to remain unused by these users.From an API standpoint, how can we provide a simpler option to disable the whole development shell and friends for this target audience (non-Haskell developer users)?
The text was updated successfully, but these errors were encountered: