Paul-Elliot Anglès d'Auriac
Paul-Elliot Anglès d'Auriac
Sure! Thanks for your answer and enjoy your vacation.
Oh no, I did not think about that... Thanks for pointing it out. Having to escape them seems cumbersome: `[` are used too often in `odoc`...
The doc seems not to be perfectly up to date with regards to code blocks, but one can [specify a language](https://ocaml.github.io/odoc/odoc_for_authors.html#language_headers) as well as some other metadata information in a...
Yes, I think 2. could be OK, but let's continue a bit the list before choosing :) 4. Like 2 but without `@` in the closing bracket: ``` {@ @tag...
> Regarding 6, I think code blocks are sufficient for that. For example {@mermaid eval=true […]} or something like that. Yes, mermaid was a bad example... Maybe a custom kind...
Another option that was suggested (I'm collecting them): Base the scope of the tag on indentation: ``` @return [foo] which for bla This is also in the tag scope since...
Regarding 6, let me add that we could slightly modify it to distinguish inline and block "extension nodes" : ``` This element is {%blink special} and inline. {%%example This one...
We discussed this during the dev meeting. First, we do not want a grouping syntax independently of tags, as proposed in 5. and 6. Indeed, custom tags already exist in...
Similarly, `module A = struct end` is valid but `mod ule A = struct end` is not. For me, the issue with ``` @return { blibli } ``` makes it...
No, we still cannot include multiple paragraphs in a tag.