DapperLib / DapperLib/Dapper

Feature Request: Add SplitAfter parameter as alternative to SplitOn

Open
#2,154 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
18.4k
Forks
3.7k
Avg merge
5h 8m
Merged PRs (30d)
1

Description

Sometimes, especially when the list of columns in the select is dynamically generated, it'd be more convenient to provide a column to split after, instead of column to split on.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Search the repository for the existing SplitOn handling and related tests to understand how split columns are selected. Add the requested SplitAfter alternative while preserving current SplitOn behavior, and verify that dynamically generated select-column lists can use it as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend-api-design
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.