Feasibility of generating Signify types from Python type hints via OpenAI

[iFergal]

As Signify can in theory be written in any language, it would be hugely beneficial to generate Signify types from KERIA OpenAPI docs dynamically, so type updates can flow automatically to implementations.

Additionally, the KERIA OpenAPI docs are quite outdated, and contain a number of syntax errors so this would be a good reason to keep them up to date. Rather than defining the type in yaml it would be good to generate type hints which can be used to make KERIA more robust too, and programmatically generate the OpenAPI docs from those type hints.

This spike should take the IdentifierCollectionEnd, and:

• Create type hints for any API responses
• Programmatically use these in the OpenAPI docs
• Generate TypeScript types in Signify-TS for any methods using this endpoint.

Note: It might be helpful to temporarily adjust specing.py to only generate OpenAPI docs for this endpoint to skip over the other syntax errors for now.

[Sotatek-Patrick-Vu]

PRs for demo:
Signify-ts: cardano-foundation/signify-ts#9
Keria: #5

[Sotatek-Patrick-Vu]

Some changes for:

1. keria:

• Define dataclass and convert it to schema of apispec
• Add 2 new deps: marshmallow_dataclass and marshmallow_oneofschema
• The spec.yaml always be served in http://keria:3902/spec.yaml

2. signify-ts

• Add script to generate TS types before building
• Add lib openapi-typescript in global, not production
• ignore generated TS types file in .gitignore
• Add a new test file to test new generated TS types

Here output files:

output.zip