Skip to content
Snippets Groups Projects
  • Markus Armbruster's avatar
    f7400483
    keyval: Restrict key components to valid QAPI names · f7400483
    Markus Armbruster authored
    
    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: default avatarMarkus Armbruster <armbru@redhat.com>
    Reviewed-by: default avatarKevin Wolf <kwolf@redhat.com>
    Message-Id: <1488317230-26248-20-git-send-email-armbru@redhat.com>
    f7400483
    History
    keyval: Restrict key components to valid QAPI names
    Markus Armbruster authored
    
    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: default avatarMarkus Armbruster <armbru@redhat.com>
    Reviewed-by: default avatarKevin Wolf <kwolf@redhat.com>
    Message-Id: <1488317230-26248-20-git-send-email-armbru@redhat.com>