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.

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

Table.input instead of Table.new #11612

Merged
merged 6 commits into from
Nov 21, 2024
Merged

Conversation

vitvakatu
Copy link
Contributor

Pull Request Description

Closes #11434

Screenshot 2024-11-20 at 5 44 27 PM

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

  • The documentation has been updated, if necessary.
  • Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
  • All code follows the
    Scala,
    Java,
    TypeScript,
    and
    Rust
    style guides. In case you are using a language not listed above, follow the Rust style guide.
  • Unit tests have been written where possible.
  • If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
    or the Snowflake database integration, a run of the Extra Tests has been scheduled.
    • If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

CHANGELOG.md Outdated
Comment on lines 32 to 33
- [Table Input Widget is now used on Table.input method instead of
Table.new][11612].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would explain more for users not accustomed to our libs. Maybe "Table widget is now matched for Table.input code, and the columns are parsed"...

'Table.input 14',
'Table.input array1',
"Table.input ['a', [123]]",
"Table.input [['a', [123]]]",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides this line, all other cases should have '123' - otherwise we could get false positive (for example, we want to test that we won't match against a column name which is a function call (line 182), but even if the code has a bug and we do match, the test still passes because of number presence.

"type": "method",
"module": "Standard.Table.Table",
"name": "input",
"arguments": [],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would put the argument here in case someone in the future would make a test with connecting to input args.

@vitvakatu vitvakatu added the CI: Ready to merge This PR is eligible for automatic merge label Nov 21, 2024
@jdunkerley jdunkerley merged commit 80ae582 into develop Nov 21, 2024
33 of 37 checks passed
@jdunkerley jdunkerley deleted the wip/vitvakatu/table.input branch November 21, 2024 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-gui CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Table Editor Widget - Parse cells to make proper column types.
3 participants