Martin Bjorklund <[email protected]> writes: > Ladislav Lhotka <[email protected]> wrote: >> Hi Ian, >> >> On Thu, 2017-12-21 at 10:42 +0100, Ian Farrer wrote: >> > Hi, >> > >> > I’m just looking at the guidance on wrapping long lines given in Section >> > 3.1. >> > Unfortunately, this doesn’t cover the case where I refer to a long path. >> > E.g: >> > >> > augment /nat:nat/nat:instances/nat:instance/nat:mapping-table/nat:mapping- >> > entry: >> > >> > In this case, the total length (unindented) is 80 characters, 82 indented >> > and >> > the path is 72 characters. Moving the path onto it’s own line with indents >> > will exceed the 72 character limit, so I need a line break in the path. >> > What’s >> > the correct way to do this? >> >> XPath syntax permits whitespace between tokens, but the argument of >> "augment" is >> a schema node identifier and not XPath. The ABNF productions for schema node >> identifiers do not permit whitespace but you can always use string >> concatenation: >> >> augment "/nat:nat/nat:instances/nat:instance/" >> + "nat:mapping-table/nat:mapping-entry"; > > But this is in the YANG source; I think Ian asked about the tree > diagram syntax. Maybe the corresponding syntax in the tree diagram
Oh, sorry, I thought is was about 6087bis. Lada > could be simply: > > augment /nat:nat/nat:instances/nat:instance > /nat:mapping-table/nat:mapping-entry: > > Or even simpler, maybe we can say that any string in the tree diagram > syntax can follow the YANG string rules. > > > > /martin -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
