qapi/schema: assert resolve_type has 'info' and 'what' args on error
resolve_type() is generally used to resolve configuration-provided type names into type objects, and generally requires valid 'info' and 'what' parameters. In some cases, such as with QAPISchemaArrayType.check(), resolve_type may be used to resolve built-in types and as such will not have an 'info' argument, but also must not fail in this scenario. Use an assertion to sate mypy that we will indeed have 'info' and 'what' parameters for the error pathway in resolve_type. Note: there are only three callsites to resolve_type at present where "info" is perceived by mypy to be possibly None: 1) QAPISchemaArrayType.check() 2) QAPISchemaObjectTypeMember.check() 3) QAPISchemaEvent.check() Of those three, only the first actually ever passes None; the other two are limited by their base class initializers which accept info=None, but neither subclass actually use a None value in practice, currently. Signed-off-by: John Snow <jsnow@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com> Message-ID: <20240315152301.3621858-12-armbru@redhat.com>
This commit is contained in:
parent
10755a9536
commit
802a3e3f74
@ -996,6 +996,7 @@ class QAPISchema:
|
||||
def resolve_type(self, name, info, what):
|
||||
typ = self.lookup_type(name)
|
||||
if not typ:
|
||||
assert info and what # built-in types must not fail lookup
|
||||
if callable(what):
|
||||
what = what(info)
|
||||
raise QAPISemError(
|
||||
|
Loading…
Reference in New Issue
Block a user