Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upDataFrame field names: open thread #229
Comments
This comment has been minimized.
This comment has been minimized.
|
Option 3 is what is enforced by Rubocop on our RoR projects. |
This comment has been minimized.
This comment has been minimized.
|
Let's go with Option 3 then for similarity across projects? (and I think it'll look nice too) |
ruebot
added this to In Progress
in DataFrames and PySpark
May 21, 2018
ruebot
added this to To Do
in 1.0.0 Release of AUT
Aug 13, 2018
ruebot
moved this from In Progress
to ToDo
in DataFrames and PySpark
Aug 13, 2018
ruebot
added
the
discussion
label
Aug 20, 2018
ruebot
added a commit
that referenced
this issue
Jul 17, 2019
ianmilligan1
closed this
in
f35d54e
Jul 18, 2019
1.0.0 Release of AUT
automation
moved this from To Do
to Done
Jul 18, 2019
DataFrames and PySpark
automation
moved this from ToDo
to In review
Jul 18, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
lintool commentedMay 18, 2018
Open thread for discussion: naming conventions for DF fields? Options include:
SourceUrlsourceUrlsource_urlI've been doing (1), but now that I look at the DF queries, I think (3) will "look better". I don't have strong opinions either way, but we should decide on something and make everything consistent.
BTW, the heuristic of "use whatever is the dominant convention in the native language" doesn't help here... because DFs will be natively implemented in Scala, but I assume frequently access in Python.