PacoVK
PacoVK
This issue is quite old, is there still something to do? Otherwise we should close it
Thanks for this report @datenbrille i will take a look into it as soon as i find time 👍
Hey @arutscheidt this is strange because the [script source](https://github.com/docToolchain/docToolchain/blob/ng/dtcw.ps1#L12) references the 3.3.1 Maybe you hav set the `DTC_VERSION` in your environment, which would take precedence over the script version. Can...
@MichaelRossner thanks again, this is a known "bug" :) While i like this change, it may introduce the same "bug" for others depending how they set their API URL. Furthermore...
@MichaelRossner PR would be awesome if you feel comfortable with it. Indeed this is one of the open things that came along with the heavy refactoring of the task. However,...
While i was reviewing, i can see you added some languages, but you do not load them and also do not specify them in the asciidoctor-attributes https://docs.asciidoctor.org/asciidoctor/latest/syntax-highlighting/highlightjs/#load-support-for-additional-languages
> which ones should we add? I would say all that we integrate and deliver with docToolchain, because why should we add the source files if we never use it?...
Seems like the parse needs further configuration here. After using ``` const content = parse(inputGivenAbove, {blockTextElements: {code: true}}) const codeElements = content.querySelectorAll('pre > code') ``` the output is now as...
I think a cleaner way than using `@ts-ignore` or `@ts-expect-error` is to instanciate the headers with ``` const headers = AxiosHeaders.from({ "Content-Type": "application/json", }) as AxiosRequestHeaders; ```
@houserockr tganks for reporting. just to put it into context, did you use a docToolchain version like 2.x and it worked or did you just start working with docToolchain. That...