Alexandre Mutel
Alexandre Mutel
> Is there a way to achieve this, or am I thinking about it wrong? Unfortunately, CppAst has been designed to mainly parse headers for codegen/interop scenarios. So, it took...
Yes, this is what I do for example in a static website generator [here](https://github.com/lunet-io/lunet/blob/6aca1c930003c39322d6e68146dd0591b01a7082/src/Lunet.Markdig/MarkdownPlugin.cs#L102-L192) but the resolution is specific to my case (e.g. central place to resolve all links...etc.) But...
When markdig was implemented, it was based on pandoc behavior. The parsing of pipe tables is a complicated beast, and as this library is mainly in maintenance mode, I won't...
Similar issue to #97. Probably has won't fix.
Thanks. It looks ok at a quick glance.
Indeed, seeing more changes coming, I agree the points from @MihaZupan
Similarly to my comment https://github.com/xoofx/Tomlyn/issues/101#issuecomment-2765741698 Tomlyn runtime model was not designed to offer precise control of trivias (whitespaces, comment...etc.) and solving that is non-trivial. Only `DocumentSyntax` can achieve this.
As per the 1.0 specs [here](https://toml.io/en/v1.0.0#inline-table) > Inline tables are intended to appear on a single line. A terminating comma (also called trailing comma) is not permitted after the last...
Unfortunately, the normalize renderer does not support tables #155 (and many other extensions) I never got it finished, as it was way too much work.
Comments are only roundtrip-able if you are using `DocumentSyntax` and `Toml.Parse(string)`. Keeping comments on a runtime model that can be declared quite differently from how it is serialized is what...