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
..
sqlite	feat(db): add error_type, error_message, rename error -> error_traceback to session_queue table	2024-05-24 20:02:24 +10:00
sqlite_migrator	feat(db): add error_type, error_message, rename error -> error_traceback to session_queue table	2024-05-24 20:02:24 +10:00
__init__.py	feat(backend): organise service dependencies	2023-10-12 12:15:06 -04:00
graph.py	fix(app): openapi schema generation	2024-05-30 12:03:03 +10:00
invocation_context.py	refactor: remove all session events	2024-05-27 09:06:02 +10:00
pagination.py	feat(api): chore: pydantic & fastapi upgrade	2023-10-17 14:59:25 +11:00