Failed to render norg table when inline code contains pipe character

Goal: Successfully render a norg table where an inline code span contains a pipe character without triggering a parsing error.

In the current norg syntax, the pipe ('|') is interpreted as a table cell delimiter, and it is unclear whether escaping mechanisms such as a backslash or backtick inside code spans are supported to treat the pipe as literal content. The documentation does not specify the required escape sequence, leading to inconsistent behavior across parsers and potential render failures.

What is the correct escape sequence for a pipe character inside inline code within a norg table? Does the norg parser recognize a backslash‑escaped pipe ('\\|') or a backtick‑escaped pipe ('`|`') as literal? Is there a configuration option to disable pipe splitting inside code spans?