Kotlin / Kotlin/dataframe

Inline some type aliases in public API, part 2

Open
#1,866 1 comment 0 reactions 0 assignees View on GitHub
good first issue
Dominant language
Kotlin
Stars
1.1k
Forks
83
Avg merge
4d 12h
Merged PRs (30d)
30

Description

Follow up of #906

The same as in #906 needs to be done, but for the following aliases as well:

- AnyCol,
- AnyColumnReference,
- AnyColumnGroupAccessor,
- StringCol,
- ColumnGroupReference

The changes should not include internal usages, and the declarations of the aliases themselves should not be removed. The main idea is to make code completion in the public API cleaner.

Contributor guide

Open the contributing guide

Research direction

Start by reading issue #906 and tracing the public API declarations that use AnyCol, AnyColumnReference, AnyColumnGroupAccessor, StringCol, and ColumnGroupReference. Check which usages are public versus internal, then verify that only public signatures inline the aliases, the alias declarations remain, and code completion presents the cleaner API.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
developer-experience
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.