-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate public get dags to fastapi #42196
Migrate public get dags to fastapi #42196
Conversation
I like using the |
02efc72
to
2ba1d85
Compare
Looks like Test OpenAPI client CI is trying to fetch endpoints that we haven't built yet? |
Rebasing will fix that. We did a revert that caused that. I just merged the final revert. |
2ba1d85
to
3be2249
Compare
3be2249
to
cdfa566
Compare
CI should be green now, it took some time but there was issues with |
Unrelated mypy failure on providers, merging |
Added the breaking label, because the Might remove later if we implement it. |
This comment was marked as resolved.
This comment was marked as resolved.
* Migrate public get dags to fastapi * Fix CI * Fix CI lowest dependency resolution
The `eval-type-backport` is a tool to replace some of the controversial new type hints added with `from future imoport __annotations__` to "classic" type hint (| and list - into `Union` and `List`). This helps to battle some of the issues where Pydantic has troubles when they are used for classes that Pydantic uses. The library was initially added in apache#42196 but it was added for all Python versions - this change limits it only to Python < 3.10
The `eval-type-backport` is a tool to replace some of the controversial new type hints added with `from future imoport __annotations__` to "classic" type hint (| and list - into `Union` and `List`). This helps to battle some of the issues where Pydantic has troubles when they are used for classes that Pydantic uses. The library was initially added in #42196 but it was added for all Python versions - this change limits it only to Python < 3.10
…e#44294) The `eval-type-backport` is a tool to replace some of the controversial new type hints added with `from future imoport __annotations__` to "classic" type hint (| and list - into `Union` and `List`). This helps to battle some of the issues where Pydantic has troubles when they are used for classes that Pydantic uses. The library was initially added in apache#42196 but it was added for all Python versions - this change limits it only to Python < 3.10 (cherry picked from commit 2948338) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
… (#44315) The `eval-type-backport` is a tool to replace some of the controversial new type hints added with `from future imoport __annotations__` to "classic" type hint (| and list - into `Union` and `List`). This helps to battle some of the issues where Pydantic has troubles when they are used for classes that Pydantic uses. The library was initially added in #42196 but it was added for all Python versions - this change limits it only to Python < 3.10 (cherry picked from commit 2948338)
… (#44315) The `eval-type-backport` is a tool to replace some of the controversial new type hints added with `from future imoport __annotations__` to "classic" type hint (| and list - into `Union` and `List`). This helps to battle some of the issues where Pydantic has troubles when they are used for classes that Pydantic uses. The library was initially added in #42196 but it was added for all Python versions - this change limits it only to Python < 3.10 (cherry picked from commit 2948338)
… (#44315) The `eval-type-backport` is a tool to replace some of the controversial new type hints added with `from future imoport __annotations__` to "classic" type hint (| and list - into `Union` and `List`). This helps to battle some of the issues where Pydantic has troubles when they are used for classes that Pydantic uses. The library was initially added in #42196 but it was added for all Python versions - this change limits it only to Python < 3.10 (cherry picked from commit 2948338)
Related to: #42159
This is the first step to get the endpoint we need. This add the
get_dags
endpoint in the public part of the fastapi API. This is iso functional in terms of feature as to what we have on the current public api. Only difference is that permissions are not yet handled we would need #42019.Also I removed for now the
field
param allowing for partial response of only subfields. This is a bit harder to handle and changes dynamically the response model of the endpoint. Also this does not improve much because the full object is already loaded by the ORM, we just save some serialization and response size. (endpoint is paginated anyway). We can work on that if we need it.A follow up PR will come to add new features to that endpoint as requested in the related issue to fulfill UI requirements.