F15.6 — Framework-neutral fixtures
| State | New |
| Parent | E15 |
| Tags | deferred |
| Predecessors | F15.3 |
| Source | E15 design, idea django-optional-areas (retired into E15) |
| Entry criteria | a SQLAlchemy application needs seed data from workbooks, and the model-vocabulary natural-key rules are adopted |
No stories yet.
Move workbook reading, sheet and column validation and ColumnType conversion
from rn_forge.django.fixtures into rn-forge-data, leaving Django's
loaddata JSON output and load_data in rn-forge-django, and add a
SQLAlchemy loader that follows the shared natural-key rules.
Context
The design separates the two halves. A SQLAlchemy loader needs natural-key rules that both ORMs share, which is the model-vocabulary idea.
Stories wait until the owner schedules the feature. Do not start or elaborate it before then.