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
As a knock-on effect of #1815, hpack's excellent feature of automatically generating the exported modules list from the source directory doesn't get triggered when I add new modules. This is presumably also relevant to its globbing capabilities.
So, the modification time of the package.yaml file is not the only criterion for when hpack should be run...
The text was updated successfully, but these errors were encountered:
This is also relevant to file-watch. Since hpath can watch globs, we also need to watch directories for additions that match the globs. We will also need such glob watching because cabal recently added the feature (not yet released)
Ahh, I was wondering why my workflow felt so awkward lately! I've found myself constantly touching my cabal file as I rename modules, etc, whereas before, hpack would take care of updating the cabal file automatically.
As a knock-on effect of #1815, hpack's excellent feature of automatically generating the exported modules list from the source directory doesn't get triggered when I add new modules. This is presumably also relevant to its globbing capabilities.
So, the modification time of the package.yaml file is not the only criterion for when hpack should be run...
The text was updated successfully, but these errors were encountered: