Skip to content

Releases: denful/flake-aspects

v0.7.0

13 Mar 01:33
@vic vic

Choose a tag to compare

This release allows Den v0.12.0 to have default parametric aspects without having people to use parametric {}.

What's Changed

  • allow passing defaultFunctor by @vic in #39

Full Changelog: v0.6.0...v0.7.0

v0.6.0

11 Mar 00:30
@vic vic
81a51a8

Choose a tag to compare

We now have a documentation site copied structure from Den.

An important fix at #38 where lib.types.functionTo merges the result of all function definitions, cuasing duplicates in Den. And #36 for better detecting curried aspect providers.

Some perf optimizations for Den: denful/den#255

What's Changed

  • readme by @vic in #32
  • safe fallback for class config and provides by @vic in #33
  • docs by @vic in #35
  • improve heuristic for detecting if curried by @musjj in #36
  • fix: avoid merging results of functor. dont use types.functionTo merge by @vic in #38
  • perf(core): Little performance optimizations by @vic in #40

New Contributors

  • @musjj made their first contribution in #36

Full Changelog: v0.5.0...v0.6.0

v0.5.0

17 Feb 10:05
@vic vic
f338a50

Choose a tag to compare

This release introduces the forward utility. source tests

The forward function produces an aspect that takes configurations from a sourceClass and propagates them into a targetClass's submodule. This was born from the realization of the following pattern in many different libraries:

# Home Manager has a NixOS module that expects per-user settings to be at:
home-manager.users.<userName> = { settings };
# NixOS and nix-Darwin support user-level configs at
users.users.<userName> = { settings };

similarly for hjem (hjem.users.<userName>) and nix-maid (users.users.<userName>.maid)

The forward utility was born at Den (see denful/den#160) but has now been extracted
up-streamed into flake-aspects since it only depends on flake-aspects resolution.

And can be handy for people using flake-aspects but not Den itself for easily integrate user-defined classes like homeManager, etc.

What's Changed

  • Split tests by @vic in #19
  • update README with correct test commands by @Alb-O in #22
  • Revert "Revert "Split tests (#19)"" by @vic in #26
  • Merging by @vic in #25
  • Add documentation for types.nix by @vic in #28
  • a bit of comments by @vic in #30
  • forward classes by @vic in #31

Full Changelog: v0.4.0...v0.5.0

v0.4.0

21 Nov 06:53
@vic vic
c929345

Choose a tag to compare

What's Changed

  • expose resolved modules on each aspect by @vic in #16
  • update checkmate by @vic in #17

Full Changelog: v0.3.0...v0.4.0

v0.3.0

16 Nov 10:16
@vic vic
6a6d47f

Choose a tag to compare

What's Changed

  • Remove provides.itself references and change .provides. -> ._. in readme by @esselius in #13
  • Allow parametric context-aware aspects at top-level by @vic in #14
  • Ensure top-level aspects support parametric functions by @vic in #15

New Contributors

Full Changelog: v0.2.0...v0.3.0

v0.2.0

05 Nov 07:26
@vic vic

Choose a tag to compare

Full Changelog: v0.1.0...v0.2.0

0.1.0

29 Oct 09:43
@vic vic

Choose a tag to compare

This is the first release. The library is feature complete for now, and can be used with confidence. main branch will be used for unstable version. We will be using semantic versioning for tags.

What's Changed

  • aspect dependencies via provide/require by @vic in #1
  • Default to empty flake.aspects. by @vic in #3
  • improve aspect dependencies by @vic in #4
  • test aspect providers by @vic in #5
  • s/requires/includes/ by @vic in #6
  • providers take a list of aspect names by @vic in #7
  • aspect-chain contains aspect objects nor their names. by @vic in #8
  • feat(aspect-trees): allow provided aspects to be static or parametric by @vic in #9
  • expose lib for creating new aspects option by @vic in #10
  • test new-scope without flakes by @vic in #11

New Contributors

  • @vic made their first contribution in #1

Full Changelog: https://github.com/vic/flake-aspects/commits/v0.1.0