about summary refs log tree commit diff
path: root/doc/languages-frameworks/crystal.section.md
AgeCommit message (Collapse)AuthorFilesLines
2024-03-28treewide: Fix all Nix ASTs in all markdown filesJanne Heß1-1/+5
This allows for correct highlighting and maybe future automatic formatting. The AST was verified to work with nixfmt only.
2022-12-04doc: use sri hash syntaxColin Arnott1-2/+2
The nixpkgs manual contains references to both sri hash and explicit sha256 attributes. This is at best confusing to new users. Since the final destination is exclusive use of sri hashes, see nixos/rfcs#131, might as well push new users in that direction gently. Notable exceptions to sri hash support are builtins.fetchTarball, cataclysm-dda, coq, dockerTools.pullimage, elixir.override, and fetchCrate. None, other than builtins.fetchTarball, are fundamentally incompatible, but all currently accept explicit sha256 attributes as input. Because adding backwards compatibility is out of scope for this change, they have been left intact, but migration to sri format has been made for any using old hash formats. All hashes have been manually tested to be accurate, and updates were only made for missing upstream artefacts or bugs.
2021-10-30doc/crystal: Update to mention shard.lock file generationSilvan Mosberger1-2/+2
2021-06-07doc: prepare for commonmarkJan Tojnar1-1/+3
We are still using Pandoc’s Markdown parser, which differs from CommonMark spec slightly. Notably: - Line breaks in lists behave differently. - Admonitions do not support the simpler syntax https://github.com/jgm/commonmark-hs/issues/75 - The auto_identifiers uses a different algorithm – I made the previous ones explicit. - Languages (classes) of code blocks cannot contain whitespace so we have to use “pycon” alias instead of Python “console” as GitHub’s linguist While at it, I also fixed the following issues: - ShellSesssion was used - Removed some pointless docbook tags.
2021-01-01doc: explicit Markdown anchors for top-level headings; remove metadataRyan Mulligan1-1/+1
I used the existing anchors generated by Docbook, so the anchor part should be a no-op. This could be useful depending on the infrastructure we choose to use, and it is better to be explicit than rely on Docbook's id generating algorithms. I got rid of the metadata segments of the Markdown files, because they are outdated, inaccurate, and could make people less willing to change them without speaking with the author.
2020-02-28crystal: use latest opensslworldofpeace1-1/+1
2019-08-26docs: Add Crystal language framework sectionSilvan Mosberger1-0/+71