Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

columnAt should work where at works #143

Open
sylwiabr opened this issue Apr 17, 2019 · 0 comments
Open

columnAt should work where at works #143

sylwiabr opened this issue Apr 17, 2019 · 0 comments
Assignees
@mwu-tow
Labels
Category: Feature Request Requests for library features Difficulty: Core Contributor Should only be attempted by a core contributor Priority: Medium Should be fixed in the next few sprints Type: Bug Something isn't working

Comments

@sylwiabr
Copy link
Member

As a user I suppose that there is no difference between using table.at name and table.columnAt index since both of them return Column.
The non-working example is each:
table.each (x: x.columnAt 0) returns error:
Zrzut ekranu 2019-04-17 o 10 53 46
@sylwiabr sylwiabr added Type: Bug Something isn't working Category: Feature Request Requests for library features Priority: Medium Should be fixed in the next few sprints Difficulty: Core Contributor Should only be attempted by a core contributor labels Apr 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mwu-tow mwu-tow

Labels
Category: Feature Request Requests for library features Difficulty: Core Contributor Should only be attempted by a core contributor Priority: Medium Should be fixed in the next few sprints Type: Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mwu-tow @sylwiabr