| 3 Nov 2023 |
|  aos joined the room. | 04:33:25 |
 asymmetric | infinisil: can you mark https://github.com/NixOS/nix.dev/pull/645 as ready to review? | 08:55:21 |
| asymmetric | it seems i don't have perms to do it myself, which would be handy. i can edit the content of the first post, for example. | 08:56:46 |
 @johannes.kirschbauer:scs.ems.host | It might be personal thing... I don't like those achor tags in our nix code because strictly bind our lib documentation to the current manual rendering, with those exact achor tags. Changing something in rendering (e.g. splitting in multiple pages) now means also breaking the documentation.
See [`lib.lists.foldl'`](#function-library-lib.lists.foldl-prime) but for attribute sets.
Has this been discussed in the documentation team? I'd prefer to keep the actual content un-opinionated from our rendering framework, and place neutral references, that are autoresolved instead of hard links, which break when touching the thing.
| 09:03:24 |
| @johannes.kirschbauer:scs.ems.host | * I don't like those achor tags in our nix code because strictly bind our lib documentation to the current manual rendering, with those exact achor tags. Changing something in rendering (e.g. splitting in multiple pages) now means also breaking the documentation.
See [`lib.lists.foldl'`](#function-library-lib.lists.foldl-prime) but for attribute sets.
Has this been discussed in the documentation team? I'd prefer to keep the actual content un-opinionated from our rendering framework, and place neutral references, that are autoresolved instead of hard links, which break when touching the thing.
| 09:03:34 |
| @johannes.kirschbauer:scs.ems.host | * I don't like those achor tags in our nix code because strictly bind our lib documentation to the current manual rendering, with those exact achor tags. Changing something in rendering (e.g. splitting in multiple pages) now means also breaking the documentation.
See [`lib.lists.foldl'`](#function-library-lib.lists.foldl-prime) but for attribute sets.
Has this been discussed in the documentation team? I'd prefer to keep the actual content un-opinionated from our rendering framework, and place neutral references, that are autoresolved instead of hard links, which break when touching the thing.
Is there some (un)/official guide for placing references?
| 09:04:55 |
| @johannes.kirschbauer:scs.ems.host | The only thing i found is
https://github.com/NixOS/nixpkgs/blob/master/doc/README.md
But it doesn't explain how to use references | 09:08:07 |
| @johannes.kirschbauer:scs.ems.host | * The only thing i found is
https://github.com/NixOS/nixpkgs/blob/master/doc/README.md
But it doesn't explain how to use references to other lib functions | 09:08:17 |
 infinisil | Johannes Kirschbauer @hsjobeki: I'm the main user of those. They're added by nixdoc. I'm using them because it's the only way to reference functions. | 09:12:35 |
| infinisil | I generally inspect the web elements to find them | 09:13:29 |
| @johannes.kirschbauer:scs.ems.host | In reply to @infinisil:matrix.org
I generally inspect the web elements to find them And now we depend on a certain web-elements beeing present on the same page ^^.
I'll try to find a solution for this., because it hinders us moving to newer formats. Any suggestions?
idea:
Something like
see [lib.lists.foldl]
Without any further. The rendering framework can transform this into references for achor tags, if it uses them.
I tried using a different rendering framework that uses seperate pages and doesnt have those exact anchors.
| 09:17:13 |
| @johannes.kirschbauer:scs.ems.host | In reply to @infinisil:matrix.org
I generally inspect the web elements to find them * And now we depend on a certain web-elements beeing present on the same page ^^.
I'll try to find a solution for this., because it hinders us moving to newer formats. Any suggestions?
idea:
Something like
see [lib.lists.foldl']
Without any further. The rendering framework can transform this into references for achor tags, if it uses them.
I tried using a different rendering framework that uses seperate pages and doesnt have those exact anchors.
| 09:17:39 |
