Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Migration tooling] Tables #112

Open
bmorelli25 opened this issue Dec 17, 2024 · 2 comments
Open

[Migration tooling] Tables #112

bmorelli25 opened this issue Dec 17, 2024 · 2 comments
Labels
authoring Relates to our markdown parser

Comments

@bmorelli25
Copy link
Member

bmorelli25 commented Dec 17, 2024

Conversion

Tables are rendered as:

```{table}
:width: auto
| <header> | <header> | <header> | ... |
| -------- | -------- | -------- | ... |
|  <text>  |  <text>  |  <text>  | ... |
|  <text>  |  <text>  |  <text>  | ... |
|  <text>  |  <text>  |  <text>  | ... |
|   ...    |   ...    |   ...    | ... |
```
@Mpdreamz Mpdreamz added the authoring Relates to our markdown parser label Dec 17, 2024
@Mpdreamz
Copy link
Member

We support this table syntax but also just the regular GitHub flavored style which would be a bit cleaner in this case?

e.g just:

| <header> | <header> | <header> | ... |
| -------- | -------- | -------- | ... |
|  <text>  |  <text>  |  <text>  | ... |
|  <text>  |  <text>  |  <text>  | ... |
|  <text>  |  <text>  |  <text>  | ... |
|   ...    |   ...    |   ...    | ... |

They would render better on Github too.

Sidenote: I personally dread creating tables in markdown even when my editor helps me so i'd still like a specialized syntax for this e.g

```{code-table} <path to yaml_json>
:columns: prop1, prop3, prop4
```

and maybe revisit #17

@bmorelli25
Copy link
Member Author

Added your table suggestion to #160. I'm going to keep this issue open for now as there are likely some edge cases with tables that we won't see until the bug bash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
authoring Relates to our markdown parser
Projects
None yet
Development

No branches or pull requests

2 participants