| lizmat | starting with RakuAST class documentation | 11:02 | |
| feels like the Type/RakuAST.rakudoc should be moved to a more Intro-like page, and then be updated. | 11:07 | ||
| [Coke]: would it be ok to remove the ":preamble<use experimental :rakuast>" from the code examples? | 11:08 | ||
| Geth | doc/main: e92d0dc85e | (Elizabeth Mattijsen)++ | 5 files Remove mention of experimental :rakuast Looking forward, I think "experimental :rakuast" should only be mentioned once, at the top level and some introduction. |
11:10 | |
| lizmat | yeah, I think it's ok, as we run all the test on the latest Rakudo release | 11:24 | |
| Geth | doc/main: 8aa79a7a4a | (Elizabeth Mattijsen)++ | 5 files Be consistent in markup 1. Be explicit about what code is, so don't assume that indented text will be code 2. Remove mention of "use experimental :rakuast" from preambles 3. Remove mention of ":lang<raku>" from code blocks, that *is* implicit |
11:25 | |
| lizmat | meh... looks like the CI runner for doc isn't updated yet? | 11:37 | |
| Geth | doc/main: 70eadad54e | (Elizabeth Mattijsen)++ | doc/Type/RakuAST/Doc/Block.rakudoc Some clarifications - don't use =foo as example, when the previous was =for, to avoid confusion - separate the rakudoc from the raku parts in examples |
12:01 | |
| doc/main: bf1c68b25d | (Elizabeth Mattijsen)++ | doc/Type/RakuAST/Doc.rakudoc Cleanup of RakuAST:Doc overview document |
12:02 | ||
| [Coke] | I am using a home grown docker image for docs, I'll update it. | 13:02 | |
| Geth | ¦ doc: coke self-assigned Test runner pinned on old version github.com/Raku/doc/issues/4824 | 13:04 | |
| [Coke] | Based on: FROM rakudo-star:latest | 13:10 | |
| Looks like that hasn't been pushed yet. | 13:13 | ||
|
14:38
camelia left
14:39
camelia joined
|
|||
| [Coke] | the example here: docs.raku.org/type/RakuAST.html says that "say" is in the output of hello world, but it would just be the string | 14:49 | |
| same issue with the example before it - the say is saying the output, it's not part of the AST getting parsed. | 14:50 | ||
| Geth | doc/main: 8a22fe8ce5 | (Elizabeth Mattijsen)++ | doc/Type/RakuAST.rakudoc Several tweaks and fixes Fixes #4825 |
16:26 | |
| [Coke] | lizmat: why are you reformatting the rakudoc as you go? | 16:29 | |
| lizmat | you mean adding =begin code blocks ? | ||
| [Coke] | I do not like the verbose version of "begin code" for a single line item. | ||
| lizmat | ah | ||
| [Coke] | yup. Just curious why you're doing it, is it a rakudoc v2 prep? | ||
| lizmat | no, it isn't, it's just trying to be consistent | 16:30 | |
| for the not so experienced rakudoc readers | |||
| [Coke] | ... with what? | ||
| the audience of people reading the rakudoc vs. the rendered HTML is probably very low. | |||
| lizmat | well, have some indented blocks in one place in a file, and in another we have =begin/end code blocks | ||
| [Coke] | That sort of style issue - let's agree on that first before making changes across the board. | 16:31 | |
| lizmat | ok, understood.. will change those back no worries | ||
| [Coke] | (no need to rewind those changes) | ||
| lizmat | no, let's at least be consistent about that inconsistency :-) | 16:32 | |
| [Coke] | (I also would prefer we write a test to enforce the style and then pass the test) | 16:34 | |
| we've done that with other style related items in the past | 16:35 | ||
| ... I should also relook at some of the doc tests now that we are guaranteed to have ast. | |||
| ... once we get the tests running with 2026.09 | |||
| Geth | doc/main: 089477701d | (Elizabeth Mattijsen)++ | 7 files Change description of a single line of code without preamble It should be indented with 4 spaces without =begin/end code |
16:36 | |