| commit | f740048323398ebde9575a5730bf6d9f2a237f08 | |
| author | Markus Armbruster <armbru@redhat.com> | |
| Tue, 28 Feb 2017 21:27:05 +0000 (28 22:27 +0100) | ||
| committer | Markus Armbruster <armbru@redhat.com> | |
| Tue, 7 Mar 2017 15:07:47 +0000 (7 16:07 +0100) | ||
| tree | a7fcd911721549b578079bcd8dec05849398a286 | treesnapshot (tar.gz zip) |
| parent | 069b64e3fe75c81edef6685c9941a7937a48fec4 | commitdiff |
keyval: Restrict key components to valid QAPI names
Until now, key components are separated by '.'. This leaves little
room for evolving the syntax, and is incompatible with the __RFQDN_
prefix convention for downstream extensions.
Since key components will be commonly used as QAPI member names by the
QObject input visitor, we can just as well borrow the QAPI naming
rules here: letters, digits, hyphen and period starting with a letter,
with an optional __RFQDN_ prefix for downstream extensions.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <1488317230-26248-20-git-send-email-armbru@redhat.com>
Until now, key components are separated by '.'. This leaves little
room for evolving the syntax, and is incompatible with the __RFQDN_
prefix convention for downstream extensions.
Since key components will be commonly used as QAPI member names by the
QObject input visitor, we can just as well borrow the QAPI naming
rules here: letters, digits, hyphen and period starting with a letter,
with an optional __RFQDN_ prefix for downstream extensions.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Message-Id: <1488317230-26248-20-git-send-email-armbru@redhat.com>
| tests/test-keyval.c | diffblobblamehistory | |
| util/keyval.c | diffblobblamehistory |