| 42 | | 1) Bulk representation functions must be available (configurable) per Field. |
| 43 | | 2) They should not be separate from single-value representations but use the same lazy lookup mechanism. |
| 44 | | 3) Ideally, bulk representations do not introduce a new hook, but utilize the existing Field.represent hook. |
| 45 | | 4) Ideally, we need only a few individual representation functions - most representations follow the same pattern anyway |
| 46 | | 5) Standard representation of foreign keys would fall back to the name field in the referenced record |
| 47 | | 6) Bulk representation functions should create only minimum overheads during model loading |
| | 42 | 1. Bulk representation functions must be available (configurable) per Field. |
| | 43 | 2. They should not be separate from single-value representations but use the same lazy lookup mechanism. |
| | 44 | 3. Ideally, bulk representations do not introduce a new hook, but utilize the existing Field.represent hook. |
| | 45 | 4. Ideally, we need only a few individual representation functions - most representations follow the same pattern anyway |
| | 46 | 5. Standard representation of foreign keys would fall back to the name field in the referenced record |
| | 47 | 6. Bulk representation functions should create only minimum overheads during model loading |
