Jannik
Jannik
I would like to second this request. A more specific error message should always be preferred to a less specific one. 👍
Same for me. Would be great to have this updated upstream https://github.com/facebook/docusaurus/issues/6872#issuecomment-1252009927
As I was the author of one of the tickets and still have this exact same problem I am obviously +1 for _any_ (relatively) simple solution
Is there any update on this one? I would disagree about a line break being a "presentational concern", as it works by separating two separate thoughts more than a semicolon...
I also have a scrappy ~860 line TypeScript file, that partially describes the public API. I can link it here, if somebody needs it. No guarantees about correctness and completeness...
I have the same issue.
I think you are probably reading the diff wrong. The example with the error reads as follows: 1. add markup `1` (`em`) on the stack (Stack: `em`) 2. add markup...
Would it make sense to create a VO that encapsulates "safe" markup? So that if you pass in a value of this type, it won't be escaped?
As this option is basically the auto-escaping of markdown, wouldn't it make sense to enable it by default so that it has to be explicitly disabled? Being insecure by default...
Does Flex support setting (and using) an Github API token? Because then the rate limit is 5000 req/hr, which is probably enough?