feat(clientapi): Return v2 test data

[benjamingeer]

This PR adds test requests and responses for the /v2/values route to the generated client API code.

I refactored the values E2E tests to move the generation of JSON-LD into functions and constants into SharedTestDataADM, where they can be used both by E2E tests and by client code generation.

I also refactored the TypeScript backend a bit to make the endpoint template easier to read.

Resolves #1513.

[tobiasschweizer]

That's great, thank you. Will try to integrate the generated v2 values endpoint test data in dasch-swiss/dsp-js-lib#86 and then review this PR.

[tobiasschweizer]

I cannot find test data for a create still image file value request.

[benjamingeer]

I cannot find test data for a create still image file value request.

That’s because there is no such request. A file value can only be created when creating a resource.

[benjamingeer]

https://docs.knora.org/paradox/03-apis/api-v2/editing-values.html#submit-a-file-value-to-knora

[tobiasschweizer]

Ok, I removed the unit test that would not have worked with Knora.

[tobiasschweizer]

I will think of a way to prevent clients from performing a create request for file values in the values endpoint.

[tobiasschweizer]

get-still-image-file-value-response.json contains

{"knora-api:error":"org.knora.webapi.NotFoundException: Value with UUID goZ7JFRNSeqF-dNxsqAS7Q not found (maybe you do not have permission to see it, or it is marked as deleted)","@context":{"knora-api":"http://api.knora.org/ontology/knora-api/v2#"}}

[benjamingeer]

Well, it’s a valid response, isn’t it? 😀

[tobiasschweizer]

Well, it’s a valid response, isn’t it? 😀

I like it!

I am reloading my test data and will regenerate the code to rule out a local problem.

[tobiasschweizer]

Would the simple schema be rejected?

[tobiasschweizer]

Would the simple schema be rejected?

[benjamingeer]

Would the simple schema be rejected?

Yes. Added tests for this.