Mark Moes

Results 59 comments of Mark Moes

> > The `Document` class already has a built in `id` field that is generated when the document is created. It's type is `PydanticObjectId`, which clashes with the `UUID` type...

If this were to happen, would (backwards) compatibility with dataclasses be a requirement?

> If you're using synchronous IO it wouldn't matter if it's `time.sleep` or a db query, result should be the same. I've indeed had similar results in tests with `select...

The recently released `pytest-celery` plugin is probably useful here https://github.com/celery/pytest-celery/releases/tag/v1.0.0 https://docs.celeryq.dev/projects/pytest-celery/en/latest/getting-started/first-steps.html

Yeah `|` might be sufficient indeed. But since the `query` parameter is for the frontend to spew user search queries to, `filterBy` is specifically for backends which can programmatically create...

Closing as there is currently no usecase for this. When there is, feel free to comment and/or reopen with a suggestion on how to implement it.

I suggest to use `not_authenticated` as an error type. Add this to the errorhandlerextension in nwa-stdlib, and then this PR should be updated to actually use it in orchestrator-core https://github.com/workfloworchestrator/orchestrator-core/pull/500