Kristof Gilicze

Recent on-boarding experience with `django-ninja`: Everything was clean and as expected ( _I did not even need the docs, everything was super intuitive._ ), up until the return schema handling....

Ok! Is an `InferringRouter` something that will be eventually included in the module, or you prefer to keep the module API in sync with FastAPI?

Considering this is only the integration of [**Laravel**](https://github.com/laravel/laravel) with **[vue-element-admin](https://github.com/PanJiaChen/vue-element-admin.)**, i really don't see why would it diverge from the original repo. Ideally it should follow both Laravel and vue-element-admin...

I can see why this make sense for the django integration. Common features working out-of-the-box (with a few lines of settings.py) is expected there. [DRF style API](https://www.django-rest-framework.org/api-guide/authentication/ ) would be...

core implementation should be reused between integrations. The django way to configure stuff is in the `settings.py`. I think it is already a little weird that I set the schema...

If you have multiple views, then I agree the 'global' setting does not make sense. I had a closer look at how DRF handles the auth classes. ... there is...

I would also prefer if I could put it under ./cypress, or anywhere else for that matter. I have enough top-level folders without. Willing to pick this up, if no...