-
Notifications
You must be signed in to change notification settings - Fork 326
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
First part of AWS S3 API, various small fixes. #6973
Conversation
std-bits/table/src/main/java/org/enso/table/data/column/storage/type/StorageType.java
Outdated
Show resolved
Hide resolved
15fb641
to
e483321
Compare
0619f15
to
e1339c5
Compare
Ability to get profiles and create provider. Initial S3 functionality - list buckets.
Put default implementation on Storage itself. Move computation to ObjectStorage.
Removed `parse_uri` as same as `to_uri`.
Supports missing day or missing year. Uses US Locale.
Support Locale in Date parse.
Align API with other parse methods.
Delete html file.
Dropdown for Date_Time formats. Fix issue with get_annotation for Date_Time.
@@ -62,11 +62,10 @@ type File | |||
|
|||
example_new = File.new Examples.csv_path | |||
new : (Text | File) -> File | |||
new path = | |||
new path:(Text|File) = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably discuss about the best practices.
For me, the preferred syntax in cases like this would be
new path:(Text|File) = | |
new (path : Text|File) = |
IMO it is more readable, it is closer to languages like Scala. But it is just a personal preference, I'm open to discussion. But I think ideally we should agree on one convention and try to use it consistently as a team.
I think the (x : A)
one is used a bit more commonly throughout the codebase, that's why I'm nitpicking here.
distribution/lib/Standard/Base/0.0.0-dev/src/Widget_Helpers.enso
Outdated
Show resolved
Hide resolved
distribution/lib/Standard/Database/0.0.0-dev/src/Data/Column.enso
Outdated
Show resolved
Hide resolved
std-bits/table/src/main/java/org/enso/table/data/column/storage/Storage.java
Outdated
Show resolved
Hide resolved
std-bits/table/src/main/java/org/enso/table/data/column/storage/type/StorageType.java
Outdated
Show resolved
Hide resolved
std-bits/table/src/main/java/org/enso/table/data/column/storage/type/StorageType.java
Show resolved
Hide resolved
std-bits/table/src/main/java/org/enso/table/data/column/storage/type/StorageType.java
Show resolved
Hide resolved
distribution/lib/Standard/Table/0.0.0-dev/src/Internal/Widget_Helpers.enso
Outdated
Show resolved
Hide resolved
@@ -0,0 +1,645 @@ | |||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if we should commit the package lock for this tool.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure, toplevel has package-lock committed. I guess there's no harm in it being here too. If it's a problem we can remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good.
Some comments with suggestions in line.
I'm worried about the potential duplication of logic for unifying the types, I feel like it's quite easy to get it to be inconsistent. It's not a problem to be solved in this PR tho - but maybe worth chatting about it sometime.
(btw. the examples next to formats for date/time are just pure gold! I think it's a very cool idea that may be worth expanding into other places) |
# Conflicts: # CHANGELOG.md
Ah, and as I was mentioning - I think we need to figure out some way to test S3 and related stuff on CI relatively ASAP - while I appreciate we don't want to make our default checks too slow, the nightly check and an opt-in label to run the additional checks on a specific PR would be really useful - otherwise it's just too easy to introduce breaking changes. |
- Add type detection for `Mixed` columns when calling column functions. - Excel uses column name for missing headers. - Add aliases for parse functions on text. - Adjust `Date`, `Time_Of_Day` and `Date_Time` parse functions to not take `Nothing` anymore and provide dropdowns. - Removed built-in parses. - All support Locale. - Add support for missing day or year for parsing a Date. - All will trim values automatically. - Added ability to list AWS profiles. - Added ability to list S3 buckets. - Workaround for Table.aggregate so default item added works.
Pull Request Description
Mixed
columns when calling column functions.Date
,Time_Of_Day
andDate_Time
parse functions to not takeNothing
anymore and provide dropdowns.Screenshots
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
./run ide build
.