We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
spark-daria follows the standard Scala / Java deep nesting package convention that's annoying when importing code.
Users currently need to import code like this: import com.github.mrpowers.spark.daria.sql.ColumnExt._
import com.github.mrpowers.spark.daria.sql.ColumnExt._
I noticed that some libraries are deviating from these Scala conventions and offering imports like this: import utest._.
import utest._
Maybe we can change the package structure so users can import code like import mrpowers.daria.sql.ColumnExt._? Thoughts @nvander1 / @manuzhang...?
import mrpowers.daria.sql.ColumnExt._
The text was updated successfully, but these errors were encountered:
Yes, the package name is too long although I don't have a good idea for a shorter one. Maybe daria._ is enough ?
daria._
Sorry, something went wrong.
No branches or pull requests
spark-daria follows the standard Scala / Java deep nesting package convention that's annoying when importing code.
Users currently need to import code like this:
import com.github.mrpowers.spark.daria.sql.ColumnExt._
I noticed that some libraries are deviating from these Scala conventions and offering imports like this:
import utest._
.Maybe we can change the package structure so users can import code like
import mrpowers.daria.sql.ColumnExt._
? Thoughts @nvander1 / @manuzhang...?The text was updated successfully, but these errors were encountered: