You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2017/09/06 03:53:01 UTC
[jira] [Updated] (OPENMEETINGS-1691) config keys/values need to be
unified
[ https://issues.apache.org/jira/browse/OPENMEETINGS-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik updated OPENMEETINGS-1691:
-------------------------------------------
Description:
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
true/false
{code}
This also have to be unified
was:
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
> 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
> true/false
> {code}
> This also have to be unified
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)