We use mdx v3 format for our documentation site under Docusaurus platform.
I encountered some compilation issues during the build process because of some characters such as { or < found in markdown files.
NOTE: The { character is used for opening JavaScript expressions whereas the < character is used for opening JSX tags. Thus, if MDX finds the expression inside { } or <> invalid, it will fail.
For example, I can’t get Crowdin to retain “\” between “]” and “{” in the following expression: \[\]\{uint, \[33\]byte\} \(Go\)
Crowdin simply renders this string as []{uint, [33]byte} (Go) when generating md file.
I could find some parser configuration parameters related to escaping but all belong to Java properties.
Is there any way to do this type of escaping in md/mdx file?
Hi @klaytn.docs ! Could you please share the link to the string in your project as an example? or at least the string itself here and let us know the file name where it is located
Just let me know whether or not it’s something that needs a fix or implementation on your side, please. It’s because I need to look for a workaround myself if I can’t get one from you or this community.
Maybe, you don’t a plan for supporting this kind of feature for the moment due to the lack of bandwidth or something. Or it’s included in TODO already but not started yet. Or still implementing and testing (if this is the case, let me know estimated date if possible). Any kind of update would be appreciated a great deal.
Our CI pipeline from Crowdin to Github has been broken in part. We need to make a additional PRs repeatedly whenever an automatic “New Crowdin updates” PR that contains the problematic files has been approved.
Thank you for the feedback.
We use yarn build for compilation using Github actions.
You can see the details about the compilation errors here which were resolved by restoring escaping backslashes.