Change Details

Instead of only writing the field where the error is occuring, we should write out the entire path to that value. [Based on: https://datatracker.ietf.org/doc/html/rfc6901]

Instead of only writing the short path pointing to where an error has occured, we should write out the entire path to that value. [Based on: https://datatracker.ietf.org/doc/html/rfc6901] For example, in the `statement-data-invalid-field` error, currently the error response contains the path to only contain the field name that has the invalid value and we should change it to include more information to the path `/value/path` (in the example here) Acceptance criteria: * All error responses containing the path field should be extended to have the syntax as is expected for JSON pointer ''{F48052657}

Instead of only writing the fieldshort path pointing to where thean error ihas occuringed, we should write out the entire path to that value. [Based on: https://datatracker.ietf.org/doc/html/rfc6901] For example, in the `statement-data-invalid-field` error, currently the error response contains the path to only contain the field name that has the invalid value and we should change it to include more information to the path `/value/path` (in the example here) Acceptance criteria: * All error responses containing the path field should be extended to have the syntax as is expected for JSON pointer ''{F48052657}