DenverCoder1/table2ascii

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

Open

#104 opened on May 16, 2023

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Python (17 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (75 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

 +-----+---+---+---+---+-----+
 | 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.

Contributor guide

Research direction
Implement a new merge direction UP that allows rows to span across multiple rows, similar to how Merge.LEFT works for columns.
Tech stack
python
Domain
clitooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70