We are currently adding a computed property for the aliased url property and it's output as sibling to original uri value. It's a bit unintuitive and inconsistent with standard uri output in what users would expect from jsonapi.
Add a uri custom field to field and set a value for it in sample entity. Observe the output in jsonapi that provides a separate property for alias as sibling to original value.
Create a custom DataType and Normalizer plugin for uri and return the jsonapi output as an array containing uri & url.
Remove existing computed property and apply new data type as replacement in the properties declaration.
Patch forthcoming.
n/a
Values in jsonapi for uri will now be returned as object containing uri and url vs. a simple string.
uri property definition will be using the new DataTypeDefinition.
Fixed
2.0
Code
Issue #3411781 by apmsooner: Create a custom DataType and normalizer for...