[
https://issues.apache.org/jira/browse/AVRO-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niels Basjes updated AVRO-1828:
-------------------------------
Attachment: AVRO-1828-2016-04-28.patch
This is the .editorconfig file for .sh, .xml and .java.
This patch also includes all these changes for the affected files:
- Remove trailing spaces and tabs
- Remove (leading) tabs
For the files where there were leading tabs I fixed the indentation (like in
the toplevel build.sh and the build.sh scripts for several of the languages)
I chose not to touch the leading tabs in the documentation files at this moment.
This is mostly about spaces and tabs; so after applying this patch a command
like {{git diff -w}} will yield almost no changes.
I need to run the full test set (all languages) on this one.
I ran Java and that passed.
> Add EditorConfig file
> ---------------------
>
> Key: AVRO-1828
> URL: https://issues.apache.org/jira/browse/AVRO-1828
> Project: Avro
> Issue Type: Improvement
> Reporter: Niels Basjes
> Assignee: Niels Basjes
> Attachments: AVRO-1828-2016-04-28.patch
>
>
> I was working with Apache Flink last week and they recently implemented
> http://editorconfig.org/ ( see here
> https://github.com/apache/flink/blob/master/.editorconfig )
> Essentially this is a very simple config file that instructs a great many
> editors to adhere to the main coding standard choices (things like character
> encoding, tabs v.s. spaces , newlines, etc) for a specific project on a per
> file type basis.
> When someone opens the project in a intelliJ then this will automatically use
> these settings.
> Proposal:
> # We implement this for Avro at the root level with global defaults.
> # We implement a specific file per language. I think we should start with the
> top level scripting (like build.sh and pom.xml) and Java as the first
> language.
> # We fix the violations of this standard in a single commit per language.
> Note that if we don't fix those violations then later commits will be
> 'harder' to keep clean (you will see a lot of unrelated changes) because the
> IDEs will 'enforce' the standard on all touched files.
> What do you guys think?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
