-
Notifications
You must be signed in to change notification settings - Fork 323
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
Using conversions in a few places #7859
Conversation
e52972c
to
aee7296
Compare
dc747ce
to
dd20a74
Compare
Add type checking for Table in right arguments.
Convert text to HTTP_Method.
Add `expand_column` function.
Tests for JSON deserializing Date/Times.
Add placeholder for Database table.
d03a2ae
to
6021c16
Compare
distribution/lib/Standard/Base/0.0.0-dev/src/Data/Time/Date_Time.enso
Outdated
Show resolved
Hide resolved
@column Widget_Helpers.make_column_name_selector | ||
Table.expand_column : Text | Integer -> Vector | Nothing -> Text | Table -> Table ! Type_Error | ||
Table.expand_column self column fields=Nothing prefix=Nothing = |
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.
Why is this an extension method and not just a regular method inside of Table.enso
?
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.
Only because the from_objects
would make the two files so intertwined felt more natural to have it next to here.
When we refactor from_objects
, probably makes sense to fold in at that point.
distribution/lib/Standard/Table/0.0.0-dev/src/Data/Table_Conversions.enso
Outdated
Show resolved
Hide resolved
distribution/lib/Standard/Table/0.0.0-dev/src/Data/Table_Conversions.enso
Outdated
Show resolved
Hide resolved
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.
Looks good generally, just a few small comments.
Tests look great, assuming we'll add more expand_column
in the future, but I know that this is the plan 🙂
Pull Request Description
from
s into correct places:Day_Of_Week.from
removingDay_Of_Week_From
module.http
andhttps
inData.read
so it calls ontoData.fetch
giving a single entry point.URI
extensions fromStandard.Base.Data
module intoStandard.Base.Network.Extensions
.post
extension forURI
.contains_key
toJS_Object
.into
inJS_Object
:JS_Object
if present.Date
,Time_Of_Day
andDate_Time
from JSON.JS_Object
.Text
to aHTTP_Method
and type checking whereHTTP_Method
used in public APIs.Date
,Time_Of_Day
andDate_Time
inTable.from_objects
.expand_column
toTable
to expandJS_Object
to values.Table
inright
arguments (allowingColumn
s to be used).Table.set
to allow for conversion to aColumn
.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
.