[Feature Request] Support Merge.UP similar to Merge.LEFT

[aurkaxi]

 +-----+---+---+---+---+-----+
 | ID  |     Config    | Oth |
 +     +---+---+---+---+     |
 |     | A | B | C | D |     |
 +-----+---+---+---+---+-----+
 | 0x0 | 2 | 0 | 0 | 4 |  3  |
 | 0x1 | 0 | 0 | 0 | 0 |  4  |
 | 0x2 | 0 | 2 | 0 | 1 |  5  |
 +-----+---+---+---+---+-----+

Merge.LEFT allows us to let "Config" have multiple columns.
Merge.UP will allow us to let "ID", "Oth" have multiple rows.

[DenverCoder1]

Thanks for the suggestion. This feature was planned when Merge was initially created, but it turns out to be very complicated to incorporate into the current code design since the library builds tables one row at a time.

Implementing the feature properly will probably require a lot of rewriting, however, I do have a version that should work for some use cases in the feat/merge-up branch. It is not in a pypi release since there are still some issues, but it can be installed from the commit hash with the following command:

pip install git+https://github.com/DenverCoder1/table2ascii.git@e244e3a1c7e445e91dd24d1612c217370c1fb3a7#egg=table2ascii

(Or in a requirements file -- git+https://github.com/DenverCoder1/table2ascii.git@e244e3a1c7e445e91dd24d1612c217370c1fb3a7#egg=table2ascii)

Your example table should work with this version, but note that some issues are not yet resolved including:

• It is not possible to combine usage of Merge.LEFT and Merge.UP to make an area spanning multiple rows and columns.
• Text does not wrap between the two vertically merged cells. If there is text in the top cell that is merged, it will remain in the top area and not expand into the lower cell.

I don't plan to resolve these issues in the near future, but I am willing to let someone else who finds this issue and can fix the remaining issues take over the branch or start a new branch to add this feature.

Feel free to let me know if you have any questions.

[aurkaxi]

1. yes merge.left and up doesn't seem possible neither practical
2. for vertical i think text being on top is good to go.

i will test that commit. currently work around with dashtable their rst export kinda looks like ascii, but that is rst so no ascii presets. i think you might check data2rst function later.
also going through some exams, so i will test that commit later.