Repository navigation
Support for custom model class #135
Description
What problem does this solve?
In my project i use custom class that inherites from model.Model but is not detected by orm-lens
class MyCustomModel(models.Model):
...
class Person(MyCustomModel):
...
Proposed solution
Add user configuration or even better autodetect inheritance from model.Model
Alternatives you considered
No response
Activity
FROWNINGdev commentedon Oct 8, 2026
Thanks for the report, @stecik. Fixed in #136 and merged to
main. It will go out in the next release of both the extension and the CLI.There was nothing wrong with the inheritance itself. The scan only reads
models.py,abstract_models.pyandmodels/*.py, so a base living in, say,core/base.pyhad no definition to resolve against, and everything below it got dropped. The scan now follows your model's imports to the file that defines the base, so no configuration is needed. That covers:from core.base import MyCustomModeland relativefrom .base import MyCustomModelfrom core import base→class Person(base.MyCustomModel)__init__.pyFields from an abstract base show up as inherited fields on
Person, the same as when the base sits inmodels.py.One limit: the base has to live inside the workspace. If yours comes from an installed package rather than your own code, please say so here and I'll look at a setting for that case.
release: py-1.13.2, v0.19.4 — model bases outside models.py (#135) (#137