As of HSEARCH-1984 for each property that should be used for sorting a @Field must be declared. That's cumbersome for fields which should not be searchable themselves, in which case a un-indexed, un-stored fields field must be declared atm.

That case would be simplified if @SortableField itself would expose all required options (field bridge, null value token). Values configured through @SortableField itself would take precedence, as a fallback we'd inherit from the referenced @Field.