I'm trying to find out how a form field retrieved from the Application API is related to the fixture data API.
For example:
{
"comment": null,
"constraint": null,
"group": "/data/administrative_information",
"hashtagValue": "#form/administrative_information/project",
"is_group": false,
"label": "Proyecto",
"label_ref": "administrative_information/project-label",
"options": [],
"relevant": null,
"repeat": null,
"required": true,
"setvalue": null,
"tag": "select1",
"translations": {
"en": "Project",
"es": "Proyecto"
},
"type": "Select",
"value": "/data/administrative_information/project"
},
Which field in the above json tells me that the fixture is below:
{
"fields": {
"project_display_text": "Water Smart Agriculture",
"project_key_value": "water_smart_agriculture"
},
"fixture_type": "project",
"id": "1234",
"resource_uri": ""
},
{
"fields": {
"project_display_text": "Emergency Response",
"project_key_value": "emergency_response"
},
"fixture_type": "project",
"id": "2345",
"resource_uri": ""
},
In the example above, it's purely by accident that the fixture type is named project, like the field definition. It can be called something entirely different.
What links them together?