[
https://issues.apache.org/jira/browse/TINKERPOP-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP-1672.
---------------------------------------
Resolution: Won't Do
Assignee: (was: Jean-Baptiste Musso)
I took a quick look at what yamlint does to our configuration files and I can't
say that I find it more readable especially in situations where we have lists
of objects or empty values for Maps that themselves are maps. perhaps the
configuration system is just overly complex to begin with...not much to do
about that now...however, the readability appears better to me with the braces
being strategically used to keep it clear how it is structured. I'm going to
close this one - if you feel strongly that the files need to be reformatted in
some way, let's discuss further on the dev list. thanks.
> Use python-style syntax for YAML configuration files
> ----------------------------------------------------
>
> Key: TINKERPOP-1672
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1672
> Project: TinkerPop
> Issue Type: Improvement
> Components: console, server
> Affects Versions: 3.1.6, 3.2.4
> Reporter: Jean-Baptiste Musso
> Priority: Trivial
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> YAML configuration files could be made less verbose and more
> human-readable/editable by removing curly braces and commas.
> Indeed, according to [Wikipedia|https://fr.wikipedia.org/wiki/YAML]:
> {quote}
> YAML 1.2 is a superset of JSON, another minimalist data serialization format
> where braces and brackets are used instead of indentation.
> {quote}
> Most .yaml configuration files in the current codebase have these extra curly
> braces and commas. We could clean these files and use python-style
> nesting/indendation. Tools such as http://www.yamllint.com could help with
> the transition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
