We're currently building a chainlit backend with a custom react frontend and so far we're very pleased with what chainlit has to offer!
For the sake of simplicity though, we planned to define a static/wildcard route in chainlit's fastapi that simply serves our frontend instead of chainlit's integrated one, however even when we added our own wildcard route, chainlit's integrated one still took priority.
While this usecase may not be as common as deploying a custom frontend separately from the chainlit backend, I think it would be nice to be able to disable the integrated frontend route - either for when it's not used, or like in our case, for when you want to serve your custom one from the same app.
Hey 👋
We're currently building a chainlit backend with a custom react frontend and so far we're very pleased with what chainlit has to offer!
For the sake of simplicity though, we planned to define a static/wildcard route in chainlit's fastapi that simply serves our frontend instead of chainlit's integrated one, however even when we added our own wildcard route, chainlit's integrated one still took priority.
While this usecase may not be as common as deploying a custom frontend separately from the chainlit backend, I think it would be nice to be able to disable the integrated frontend route - either for when it's not used, or like in our case, for when you want to serve your custom one from the same app.