🚸 Cleaner API

[falexwolf]

VSCode builds their auto-complete completely statically. The only way to arrive at a clean API while still directly leveraging subclasses of Django Model is by making the internal Django API private.

This is now achieved when running:

lamin set private-django-api true

Also, we define Registry class methods via a meta class. Thanks, @Koncopd!

Here is an extensive conversation with Claude 3.5 Sonnet on why this seems to best compromise. Other routes we investigated were, e.g., building the Registry class via composition rather than inheritance.

Below are screenshots for the auto-complete experience in JupyterLab and VSCode.

Before	After

What still doesn't work are backwards fields that are dynamically generated by Django. These are going to be added through type annotations in another PR.

See:

• 🚸 Cleaner API lamindb-setup#792
• 🚸 Cleaner API lnschema-core#396

[github-actions]

🚀 Deployed on https://669532c2d560b12f60166dfd--lamindb-qnwk.netlify.app

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.14%. Comparing base (4f1797e) to head (4b8eae0).
Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1723      +/-   ##
==========================================
+ Coverage   92.12%   92.14%   +0.02%     
==========================================
  Files          50       50              
  Lines        5496     5476      -20     
==========================================
- Hits         5063     5046      -17     
+ Misses        433      430       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.