#12604·orm

Make PropertyAccessorInterface public API

Author: driskellCreated Sep 9, 2026Updated Sep 9, 2026

Feature Request

What

Currently the PropertyAccessor Interface appears to be internal and it would be useful to have it as public API.

Why

I used to extend ORM in previous versions with custom field definitions that vary based on configuration - these are still possible and quite easy to append to the metadata for an entity but the problem then lies in how accessing the data storage works. Currently all property accessors are internal and not public API so it's not possible to actually do anything. Where it would be useful if at least the interface was public API so that you could implement your own accessor for handling a dynamic field.

How

Remove internal from PropertyAccessor and document as something extenders can use