Converting *.in files to JSON5

[Sasha Bermeister]

Hi blink dev,

A few of us in Sydney are looking at converting CSSProperties.in (and the other *.in files) into a common format, since these files are growing larger and becoming harder to work with and maintain. We were originally looking at YAML but have now decided on JSON5, which has a lot of the same benefits as YAML but without the language complexity and unexpected behaviors.

Bug here:

https://bugs.chromium.org/p/chromium/issues/detail?id=677884

Design doc here:

https://docs.google.com/document/d/1gJanTJmakqd_HAm5GqnnfUxfG2G1koqSEZ8A-Q9Nhao/edit#heading=h.jkgiumley8dw

Initial CL is up here:

https://codereview.chromium.org/2620883002/

Feedback welcome :)

Thanks,

Sasha

[Dirk Pranke]

One follow-up note: Currently we use PYthon Literal (.pyl) files in a number of places for infra-related things today. I'd like to move those files to .json5 as well

to be consistent.

-- Dirk

[Elliott Sprehn]

Sounds like a great plan!

--
You received this message because you are subscribed to the Google Groups "platform-architecture-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to platform-architecture-dev+unsub...@chromium.org.
To post to this group, send email to platform-architecture-dev@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/platform-architecture-dev/CAEoffTBdnFOafAQ5%3Dh_3qDT5XAQFAzKfrO_eSf%3DoQwLt4Kw8fw%40mail.gmail.com.

[Elliott Sprehn]

Sounds like a great plan!

On Jan 12, 2017 2:51 PM, "Dirk Pranke" <dpr...@chromium.org> wrote:

--

[Kevin Liu]

Looks like infra is using proto3 text format as seen in the other thread.

Its format seems more verbose than our proposed JSON5 format, in particular a "list" may need to look like this (https://chromium.googlesource.com/chromium/src/+/master/infra/config/cq.cfg ):

      builders { name: "android_arm64_dbg_recipe" }

      builders { name: "android_clang_dbg_recipe" }

      builders { name: "android_compile_dbg" }

      builders { name: "android_cronet" }

      builders { name: "android_n5x_swarming_rel" }

      builders { name: "cast_shell_android" }

      builders { name: "linux_android_rel_ng" } 

Let's use JSON5 on our side since developers here are familiar with JavaScript and we don't need complex schemas desired in infra?