Skip to content

Better FastAPI interoperability #327

Description

@iwr-redmond

Description

IIUC, the current method for mixing FastAPI with Rio has some limitations:

  • The as_fastapi feature can only be called once in a Rio app
  • FastAPI is blocked by run_as_web_server
  • FastAPI is blocked by rio run

Suggested Solution

@Aran-Fey has suggested:

An alternative we can consider is making rio.App a subclass of FastAPI. That would give you convenient access to all fastapi features, while also retaining access to rio features like run_as_web_server().

Alternatives

Better documentation of the limitations for using FastAPI features in a Rio app.

Related Issues/Pull Requests

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementImproves on existing functionality - NOT a new feature

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions