Yes, that's an approach, though I still dislike the irregularity of exposing @Field properties through numericField(). Regarding the naming, agreed, but would you do it differently for a new one now, given the pattern is established for all the others. Also agreed on not using inheritance, I've changed that for SortableFieldMapping with my latest PR. It does not expose the field-level settings.