2d1d81114d
Over the last year or so I've run into several use cases where I need to parse and/or serialize URLs for use by `builtins.fetchTree` or `builtins.getFlake`, largely in order to produce _lockfile-like_ files for lang2nix frameworks or tools which use `nix` internally to drive builds. I've gone through the painstaking process of emulating `nix::FlakeRef::fromAttrs` and `nix::parseFlakeRef` several times with mixed success; but these are difficult to create and even harder to maintain if I hope to stay aligned with changes to the real parser/serializer. I understand why adding new `builtins` isn't something we want to do flagrantly. I'm recommending this addition simply because I keep encountering use cases where I need to parse/serialize these URIs in `nix` expressions, and I want a reliable solution. Co-authored-by: Eelco Dolstra <edolstra@gmail.com> Co-authored-by: John Ericson <git@JohnEricson.me> |
||
|---|---|---|
| .. | ||
| src | ||
| theme | ||
| anchors.jq | ||
| book.toml | ||
| custom.css | ||
| generate-builtin-constants.nix | ||
| generate-builtins.nix | ||
| generate-manpage.nix | ||
| generate-xp-features-shortlist.nix | ||
| generate-xp-features.nix | ||
| local.mk | ||
| quote-literals.xsl | ||
| redirects.js | ||
| utils.nix | ||