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
While handling fluent interfaces if the instruction is within parenthesis Black formats it this way:
(spark.read.parquet(path).select(columns).filter('column is not null').filter((f.size('id_list') > 1) & (f.col('operating_system') != 'iOS')))
( spark.read.parquet(path) .select(columns) .filter("column is not null") .filter((f.size("id_list") > 1) & (f.col("operating_system") != "iOS")) )
However if the instruction is not within parenthesis it formats it differently:
spark.read.parquet(path).select(columns).filter('column is not null').filter((f.size('id_list') > 1) & (f.col('operating_system') != 'iOS'))
spark.read.parquet(path).select(columns).filter("column is not null").filter( (f.size("id_list") > 1) & (f.col("operating_system") != "iOS") )
I believe it would be beneficial to force the use of parenthesis to use the better formatting style instead of the other
The text was updated successfully, but these errors were encountered:
Thanks for submitting! This is tracked in #571, so let's continue there.
Sorry, something went wrong.
No branches or pull requests
While handling fluent interfaces if the instruction is within parenthesis Black formats it this way:
However if the instruction is not within parenthesis it formats it differently:
I believe it would be beneficial to force the use of parenthesis to use the better formatting style instead of the other
The text was updated successfully, but these errors were encountered: