[jira] [Commented] (OPENMEETINGS-1691) config keys/values need to be unified

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENMEETINGS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153496#comment-16153496 ] 

ASF subversion and git services commented on OPENMEETINGS-1691:
---------------------------------------------------------------

Commit 6ac6ec5f67f4e30103c4bb345e6d5fd14e76f750 in openmeetings's branch refs/heads/master from [~solomax]
[ https://git-wip-us.apache.org/repos/asf?p=openmeetings.git;h=6ac6ec5 ]

[OPENMEETINGS-1691] config names are unified


> config keys/values need to be unified
> -------------------------------------
>
>                 Key: OPENMEETINGS-1691
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1691
>             Project: Openmeetings
>          Issue Type: Improvement
>          Components: Import/Export
>    Affects Versions: 3.3.0
>            Reporter: Maxim Solodovnik
>            Assignee: Maxim Solodovnik
>             Fix For: 4.0.0
>
>
> Currently config keys has no common naming convension, i.e. we have:
> {code}
> crypt_ClassName
> dashboard.show.chat
> default_lang_id
> sendEmailWithVerficationCode
> {code}
> I believe this have to be unified to be in format {{dashboard.show.chat}}
> Same time boolean config keys are stored as
> {code}
> 0/1
> yes/no
> {code}
> This also have to be unified



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)