Edit - Code Golf Stack Exchange

1. Home
2. Questions
3. Unanswered
4. AI Assist
5. Tags
7. Chat
8. Users
10. Companies
Stack Internal

Stack Overflow for Teams is now called Stack Internal. Bring the best of human thought and AI automation together at your work.
Try for free Learn more
Stack Internal
Bring the best of human thought and AI automation together at your work. Learn more

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

Title*

Body*

[Stack Exchange doesn't know how to transpose tables.](https://meta.stackexchange.com/a/357504/317948) Let's help.

**Given a markdown table, transpose it.**

Input assumptions:
* There will be at least two rows (including header) and two columns
* Either all cells have no leading space or all cells have exactly one leading space (you must handle both)
* If the cells have a leading space, then the widest cell in every column has exactly one trailing space, otherwise, the widest cell in every column has no trailing spaces
* All pipes line up
* The header-body separator lines of dashes extend the full width of their column, except a leading and tailing space if the table uses this
* Cell alignment (`-:`, `:-:`, etc.) is not used 
* No other extraneous spaces appear (this includes between words)
* Either all rows have a trailing pipe or no rows have a trailing pipe (you must handle both)
* Cells contain only printable ASCII, but no pipes (`|`), dashes (`-`) or any characters that need special treatment (``\``, `**`, etc.)
* All cells will have at least *some* non-space content

Output requirements:
* Trailing pipe on every row or no trailing pipes (must be consist for any one result)
* Either no leading spaces, or exactly one leading space in every cell (must be consist for any one result)
* If you produce leading spaces, then the widest cell in each column must have exactly one trailing space
* All pipes must line up
* The header-body separator must extend to the full width of the column, save for leading and trailing spaces, if used in that result
* Trailing spaces (and up to one trailing line break) are acceptable

# Test cases
## A
### Test inputs (you must handle every one of these)

```
| A header | Another header |
| -------- | -------------- |
| First    | row            |
| Second   | row            |
```
```
| A header | Another header
| -------- | --------------
| First    | row           
| Second   | row            
```
```
|A header|Another header|
|--------|--------------|
|First   |row           |
|Second  |row           |        
```
```
|A header|Another header
|--------|--------------
|First   |row           
|Second  |row           
```
### For any of the above inputs, output must be any one of the below<br> <sup>(not necessarily corresponding 1:1)</sup>
```
| A header       | First | Second |
| -------------- | ----- | ------ |
| Another header | row   | row    |
```
```
| A header       | First | Second
| -------------- | ----- | ------
| Another header | row   | row   
```
```
|A header      |First|Second|
|--------------|-----|------|
|Another header|row  |row   |
```
```
|A header      |First|Second
|--------------|-----|------
|Another header|row  |row   
```
## B
### Test inputs (you must handle every one of these)

```
| A header | Another header | Last column here  |
| -------- | -------------- | ----------------- |
| First    | 0              | more content here |
| Second   | row            | that's it!        |
```
```
| A header | Another header | Last column here 
| -------- | -------------- | -----------------
| First    | 0              | more content here
| Second   | row            | that's it!       
```
```
|A header|Another header|Last column here |
|--------|--------------|-----------------|
|First   |0             |more content here|
|Second  |row           |that's it!       |
```
```
|A header|Another header|Last column here
|--------|--------------|-----------------
|First   |0             |more content here
|Second  |row           |that's it!
```
### For any of the above inputs, output must be any one of the below<br> <sup>(not necessarily corresponding 1:1)</sup>
```
| A header         | First             | Second     |
| ---------------- | ----------------- | ---------- |
| Another header   | 0                 | row        |
| Last column here | more content here | that's it! |
```
```
| A header         | First             | Second    
| ---------------- | ----------------- | ----------
| Another header   | 0                 | row       
| Last column here | more content here | that's it!
```
```
|A header        |First            |Second    |
|----------------|-----------------|----------|
|Another header  |0                |row       |
|Last column here|more content here|that's it!|
```
```
|A header        |First            |Second    
|----------------|-----------------|----------
|Another header  |0                |row       
|Last column here|more content here|that's it!
```

If this is an answer to a challenge…

…Be sure to follow the challenge specification. However, please refrain from exploiting obvious loopholes. Answers abusing any of the standard loopholes are considered invalid. If you think a specification is unclear or underspecified, comment on the question instead.
…Try to optimize your score. For instance, answers to code-golf challenges should attempt to be as short as possible. You can always include a readable version of the code in addition to the competitive one. Explanations of your answer make it more interesting to read and are very much encouraged.
…Include a short header which indicates the language(s) of your code and its score, as defined by the challenge.

More generally…

…Please make sure to answer the question and provide sufficient detail.
…Avoid asking for help, clarification or responding to other answers (use comments instead).

Tags

Edit Summary*

Cancel

3

\$\begingroup\$ Maybe you want testcases with more columns? May the input table only contains header? \$\endgroup\$

tsh
– tsh

2021-01-05 08:22:26 +00:00
Commented Jan 5, 2021 at 8:22
1

\$\begingroup\$ Don't know about that snippet style of showing examples, it's too fiddly. Posting examples as text is way clearer. Edited post, please feel free to revert back if really want that horrible snippet style! T_T \$\endgroup\$

Noodle9
– Noodle9

2021-01-05 11:21:38 +00:00
Commented Jan 5, 2021 at 11:21
1

\$\begingroup\$ @vrintle I believe that's allowed by standard I/O rules for the site. \$\endgroup\$

Adám
– Adám

2021-01-05 19:14:16 +00:00
Commented Jan 5, 2021 at 19:14
1

\$\begingroup\$ @Arnauld Yes, fixed. Thanks. \$\endgroup\$

Adám
– Adám

2021-01-06 00:50:07 +00:00
Commented Jan 6, 2021 at 0:50
1

\$\begingroup\$ @KevinCruijssen Ooh, that's a good question. Since I didn't specify anything but "or any characters that need special treatment" and it would seem that you would need to give dashes special treatment, let's say that they can't. I'll add it. \$\endgroup\$

Adám
– Adám

2021-01-07 15:41:41 +00:00
Commented Jan 7, 2021 at 15:41

| Show 9 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author