Directly construsting the AST #131
Comments
Ericson2314
added a commit
to NixOS/nix
that referenced
this issue
Jan 9, 2024
The renaming task is splatting everything together into markdown lists. I think I want to do that with the lowdown AST; I opened kristapsdz/lowdown#131 for this purpose PR #9273 should be able to improve upon this a good bit, but I think it is still a useful stepping stone.
Ericson2314
added a commit
to NixOS/nix
that referenced
this issue
Jan 9, 2024
The renaming task is splatting everything together into markdown lists. I think I want to do that with the lowdown AST; I opened kristapsdz/lowdown#131 for this purpose PR #9273 should be able to improve upon this a good bit, but I think it is still a useful stepping stone.
|
OK I see most of the needed stuff is in |
Ericson2314
added a commit
to NixOS/nix
that referenced
this issue
Jan 12, 2024
The renaming task is splatting everything together into markdown lists. I think I want to do that with the lowdown AST; I opened kristapsdz/lowdown#131 for this purpose PR #9273 should be able to improve upon this a good bit, but I think it is still a useful stepping stone.
|
My attempt to do some of this is in NixOS/nix#9732. It's currently crashing but that might be my fault. |
Ericson2314
added a commit
to obsidiansystems/nix
that referenced
this issue
Jan 15, 2024
The renaming task is splatting everything together into markdown lists. I think I want to do that with the lowdown AST; I opened kristapsdz/lowdown#131 for this purpose PR NixOS#9273 should be able to improve upon this a good bit, but I think it is still a useful stepping stone.
Ericson2314
added a commit
to obsidiansystems/nix
that referenced
this issue
Jan 15, 2024
The renaming task is splatting everything together into markdown lists. I think I want to do that with the lowdown AST; I opened kristapsdz/lowdown#131 for this purpose PR NixOS#9273 should be able to improve upon this a good bit, but I think it is still a useful stepping stone.
Ericson2314
added a commit
to NixOS/nix
that referenced
this issue
Jan 16, 2024
The renaming task is splatting everything together into markdown lists. I think I want to do that with the lowdown AST; I opened kristapsdz/lowdown#131 for this purpose PR #9273 should be able to improve upon this a good bit, but I think it is still a useful stepping stone.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, https://github.com/nixos/nix current uses lowdown for all manner of documentation purposes. For some autogenerated documentation, we currently do things in a rather ad-hoc way. It would be much nicer to instead directly construct the lowdown AST, rather than crudely pasting together strings that lowdown later parses. Is it at all ergonomic to do this today / is there any documentation on how to do this?
The text was updated successfully, but these errors were encountered: