You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Ryan Blue (JIRA)" <ji...@apache.org> on 2016/04/12 17:42:25 UTC
[jira] [Commented] (AVRO-1828) Add EditorConfig file
[ https://issues.apache.org/jira/browse/AVRO-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15237408#comment-15237408 ]
Ryan Blue commented on AVRO-1828:
---------------------------------
Sounds good to me!
> Add EditorConfig file
> ---------------------
>
> Key: AVRO-1828
> URL: https://issues.apache.org/jira/browse/AVRO-1828
> Project: Avro
> Issue Type: Improvement
> Reporter: Niels Basjes
>
> 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)