[ios, docs] Fix formatting in Predicates & Expressions guide #11574
Conversation
- Code ticks within HTML tables do not convert. - Pipes within Markdown tables are interpreted as new columns, even within ticks.
There was a problem hiding this comment.
Wow, thanks for taking care of this! I hadn’t even gotten around to filing an issue about the formatting issues in the custom function table.
Maybe as a follow-up step sometime, we can figure out a way to reformat the custom function table as headings and prose, with separate parameter tables for each function, rather than a monolithic table that doesn’t lay out well.
| @@ -36,7 +36,7 @@ The following compound operators are supported: | |||
| `NSCompoundPredicateType` | Format string syntax | |||
| --------------------------|--------------------- | |||
| `NSAndPredicateType` | `predicate1 AND predicate2`<br />`predicate1 && predicate2` | |||
| `NSOrPredicateType` | `predicate1 OR predicate2`<br />`predicate1 || predicate2` | |||
| `NSOrPredicateType` | `predicate1 OR predicate2`<br /><code>predicate1 || predicate2</code> | |||
There was a problem hiding this comment.
By the way, I think \| also works here.
There was a problem hiding this comment.
Technically this is a bug in jazzy’s markdown parser’s order of operations, as code || block should be wrapped first and not interpreted at all.
If you try to use an escape \ within a code block, I’d expect the behavior to be code \|\| block — this is what Github and other Markdown parsers do. Jazzy also behaves this way, except (apparently) for special Markdown control characters.
Follow-up to #11472.
/cc @1ec5 @fabian-guerra @jmkiley @captainbarbosa