Skip to content

Commit

Permalink
Figured out the table formatting
Browse files Browse the repository at this point in the history
  • Loading branch information
expede committed Jul 2, 2024
1 parent 0a64f54 commit 5f4d564
Showing 1 changed file with 91 additions and 37 deletions.
128 changes: 91 additions & 37 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -191,7 +191,7 @@ For example, consider the following:
{
"args": {
"from": "[email protected]",
"to": ["[email protected]", "carol@elsewhere.example.com"],
"to": ["[email protected]", "carol@not.example.com", "dan@example.com"],
"cc": ["[email protected]"],
"title": "Meeting Confirmation",
"body": "I'll see you on Tuesday"
Expand All @@ -201,60 +201,114 @@ For example, consider the following:
```

<table>
<thead>
<tr>
<td>Selector</td>
<td>Value</td>
</tr>
</thead>
<!--
NOTE: You cannot add _any_ indentation to this table if you want
GitHub to render that big multiline code block correctly
-->
<thead>
<tr>
<td>Selector</td>
<td>Returned Value</td>
</tr>
</thead>

<tr>
<td>

`.`
<tbody>
<tr>
<td>

</td>
``` json
"."
```

<td>
</td>
<td>

```js
```json
{
"from": "[email protected]",
"to": ["[email protected]", "carol@elsewhere.example.com"],
"to": ["[email protected]", "carol@not.example.com", "dan@example.com"],
"cc": ["[email protected]"],
"title": "Meeting Confirmation",
"body": "I'll see you on Tuesday"
}
```

</td>
</tr>

<tr>
<td>

</td>
</tr>
``` json
".title"
```

</td>

<td>

<tr>
<td>
``` json
"Meeting Confirmation"
```

`.title`
</td>
</tr>

</td>
<td>
<tr>
<td>

`"Meeting Confirmation"`
</td>
</tr>

``` json
".cc"
```

</td>

<tr>
<td>

`.to[1]`

</td>
<td>

`"[email protected]"
<td>

``` json
["[email protected]"]
```

</td>
</tr>

`</td>
</tr>
<tr>
<td>

``` json
".to[1]"
```

</td>
<td>


``` json
"[email protected]"
```

</td>
</tr>

<tr>
<td>

``` json
".to[-1]"
```

</td>
<td>


``` json
"[email protected]"
```

</td>
</tr>
</tbody>
</table>

### Validation
Expand Down

0 comments on commit 5f4d564

Please sign in to comment.