You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Otto Fowler (JIRA)" <ji...@apache.org> on 2017/04/21 05:10:04 UTC
[jira] [Commented] (NIFI-452) Use consistent casing of
AllowableValues
[ https://issues.apache.org/jira/browse/NIFI-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978073#comment-15978073 ]
Otto Fowler commented on NIFI-452:
----------------------------------
Maybe the archetypes should evaluate these types of things, like a checkstyle rule
> Use consistent casing of AllowableValues
> ----------------------------------------
>
> Key: NIFI-452
> URL: https://issues.apache.org/jira/browse/NIFI-452
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 0.1.0
> Reporter: Dan Bress
> Priority: Trivial
>
> Some processors that allow for boolean values specify them as "true" and "false"
> - {{PutFTP}}
> While others specify them as "True" and "False"
> - {{InvokeHTTP}}
> Some processors allow for "REPLACE", "IGNORE", "RENAME", "REJECT", "FAIL", "NONE"
> - {{PutFTP}}
> while others allow for "replace", "ignore", "rename", "reject", "fail", "none"
> - {{PutHDFS}}
> I've seen these different schemes used:
> - lowercase
> - Pascal
> - UPPERCASE
> - dash-separated-name
> - Human readable name
> Lets pick one and go with it for all standard processors
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)