Page History

...

• 1. If field names do not contain dots (.), then only use dots to represent nested fields.
• 2. If field names contain dots, then:
  • wrap the field name with a backtick pair (`...`) by
    • adding an opening backtick at the beginning of the field name (beginning of path, or after a dot)
    • adding a closing backtick at the end of the field name (end of the path, or before the next dot)
  • if a field is wrapped and doesn't contain dots, is processed the same way: field name within the wrapping backticks is used
• 3. If field name includes backticks, then:
  • if the backticks are in a wrapping position (opening or closing a field name), then need to be escaped with backslash
    • Backslashes (/) do not need to be escaped. If backslash happen to be part of the field name and before a backtick to be escaped, then add another backslash.
  • else, backticks do not require escape
• 4. If wrapping backtick pairs are incomplete, Connect configuration must fail fast to avoid getting ambiguous paths deployed.

Examples

foo:

foo:
  bar:
    baz: val

OK: foo.bar.baz

foo

:

  bar.baz: val

OK: foo.`bar.baz`

foo

:

  bar:

    baz: val

OK: foo.`bar`.baz
OK: foo.bar.baz
ERROR: foo.`bar.baz: no pair
ERROR: foo.bar`.baz: no pair

foo:

  ba`r:

    baz: val

OK: foo.ba`r.baz
OK: foo.`ba`r`.baz

foo

:

  bar`.`baz: val

OK: foo.`bar\`.\`baz`
ERROR: foo.`bar\`.`baz`:

 no pair
ERROR: foo.`bar`.`baz`: valid but different path (see 2.1)

foo:

  b`ar.baz: val

OK: foo.`b`ar.baz`

foo:

bar\`.

`baz: val

OK: foo.`bar\\`.\`baz`

foo

:

  `bar`:

      baz: val

OK: foo.``bar``.baz
ERROR: foo.`bar`.baz: valid but different path (see 2.1)

Affected SMTs

These SMTs will include support for nested structure:

...