psychedelicious 2f9ebdec69 fix(app): openapi schema generation ... Some tech debt related to dynamic pydantic schemas for invocations became problematic. Including the invocations and results in the event schemas was breaking pydantic's handling of ref schemas. I don't really understand why - I think it's a pydantic bug in a remote edge case that we are hitting. After many failed attempts I landed on this implementation, which is actually much tidier than what was in there before. - Create pydantic-enabled types for `AnyInvocation` and `AnyInvocationOutput` and use these in place of the janky dynamic unions. Actually, they are kinda the same, but better encapsulated. Use these in `Graph`, `GraphExecutionState`, `InvocationEventBase` and `InvocationCompleteEvent`. - Revise the custom openapi function to work with the new models. - Split out the custom openapi function to a separate file. Add a `post_transform` callback so consumers can customize the output schema. - Update makefile scripts.		2024-05-30 12:03:03 +10:00
..
api	fix(events): typing for download event handler	2024-05-27 11:13:47 +10:00
assets/images	tweaks in response to psychedelicious review of PR	2023-07-26 15:27:04 +10:00
invocations	fix(app): openapi schema generation	2024-05-30 12:03:03 +10:00
services	fix(app): openapi schema generation	2024-05-30 12:03:03 +10:00
shared	tidy(nodes): move all field things to fields.py	2024-03-01 10:42:33 +11:00
util	fix(app): openapi schema generation	2024-05-30 12:03:03 +10:00
__init__.py	fix: make invocation_context.py accessible to mkdocs	2024-03-01 10:42:33 +11:00
api_app.py	fix(app): openapi schema generation	2024-05-30 12:03:03 +10:00
run_app.py	feat: single app entrypoint with CLI arg parsing	2024-03-19 09:24:28 +11:00