4 ms·

A couple thoughts. If your configuration file is so long it's unreadable in YAML, then maybe you need to break it up into more than one file? I can't imagine a

by jerrac 8y ago

A couple thoughts. If your configuration file is so long it's unreadable in YAML, then maybe you need to break it up into more than one file? I can't imagine any syntax would be easy to read once you reach more than 100 or so lines. Do any configuration file languages support type hinting? Adding (int) in front of a YAML key would be easy enough to read, and would keep some of the confusion at bay.

deleted 8y ago
[deleted]
erik_seaberg 8y ago
YAML tags work this way. E.g., 2002-04-28 is a date (because it looks like one) but !!str 2002-04-28 is a string.
- jerrac 8y ago
  I had never heard of tags before. Thanks! So, would this work? ports: https: enabled: yes !!int port: 443 Then if someone is copy/pasting and tries to use "blah" as the value, the !!int tag would cause the yaml parser to throw an error. Right?
  - spiralx 8y ago
    No, because tags specify a type for the value, not the key, so you could use ports: https: port: !!str 443 to parse the same as { "ports": { "https": { "port": "443" } } } in JSON
    - jerrac 8y ago
      Ah, I had my syntax wrong. Thanks!