Note: Although recommended, sort fields do not necessarily need to correspond to resource attribute and association names.
it is not required that sort fields are a valid resource field. I added addCustomAscendingOrder and addCustomDescendingOrder which don't fail if the provided attribute is not a valid field.
I also changed the router so that it does not fail if a custom value was provided.
I think this should be added to Spine as JSONAPI does not restrict us to have custom sort fields.
As stated in the JSONAPI documentation:
it is not required that sort fields are a valid resource field. I added
addCustomAscendingOrder
andaddCustomDescendingOrder
which don't fail if the provided attribute is not a valid field.I also changed the router so that it does not fail if a custom value was provided.
I think this should be added to Spine as JSONAPI does not restrict us to have custom sort fields.