Browse Source
We incorrectly report "FOO should be a type name" when it could also be an array. Fix that. Signed-off-by: Markus Armbruster <armbru@redhat.com> Message-Id: <20230316071325.492471-8-armbru@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com>pull/235/head
5 changed files with 11 additions and 12 deletions
@ -1,2 +1,2 @@ |
|||
event-nest-struct.json: In event 'EVENT_A': |
|||
event-nest-struct.json:1: 'data' member 'a' should be a type name |
|||
event-nest-struct.json:1: 'data' member 'a' should be a type name or array |
|||
|
|||
@ -1,2 +1,2 @@ |
|||
nested-struct-data.json: In command 'foo': |
|||
nested-struct-data.json:2: 'data' member 'a' should be a type name |
|||
nested-struct-data.json:2: 'data' member 'a' should be a type name or array |
|||
|
|||
@ -1,2 +1,2 @@ |
|||
returns-dict.json: In command 'oops': |
|||
returns-dict.json:2: 'returns' should be a type name |
|||
returns-dict.json:2: 'returns' should be a type name or array |
|||
|
|||
@ -1,2 +1,2 @@ |
|||
struct-member-invalid.json: In struct 'Foo': |
|||
struct-member-invalid.json:1: 'data' member 'a' should be a type name |
|||
struct-member-invalid.json:1: 'data' member 'a' should be a type name or array |
|||
|
|||
Loading…
Reference in new issue