Blank nodes with dash:DetailsViewer still only show the blanknode label.

[kburger]

Using client v1.17.1-rc.3, the view still renders a blank node with a dash:viewer dash:DetailsViewer as the blank node label.

[dennisvang]

I guess dash:DetailsViewer is not supported (yet):

FAIRDataPoint-client/src/utils/metadata.ts

Lines 77 to 91 in d6eacb9

	switch (fieldConfig.viewer) {
	case DASH('LabelViewer').value:
	return itemFromPath(value)
	case DASH('URIViewer').value:
	return { label: value, uri: value }
	default:
	if (fieldUtils.isDatetime(fieldConfig)) {
	return { label: moment(value).format(config.dateFormat) }
	}
	if (fieldConfig.datatype === XSD('boolean').value) {
	if (valueUtils.isTrue(value)) return { label: 'TRUE' }
	if (valueUtils.isFalse(value)) return { label: 'FALSE' }
	}
	return { label: value }
	}

The desired behavior would be as follows (from the dash:DetailsViewer docs):

Rendering: shows the details of the value using its default view shape or the shape specified using sh:node, as a nested form-like display. An example of this can be found in the Nested Forms section.

and from the Nested Forms section:

Using dash:DetailsViewer as the dash:viewer (or dash:DetailsEditor as the dash:editor - not yet supported by TopBraid) instructs a form engine to recursively "walk" into the linked resource and show its values as a sub-form of the surrounding form. The value of sh:node tells the form engine which selection of properties to display, and in which order. (In the case above, no property groups are shown for nested forms, to reduce the complexity to users).

[dennisvang]

Currently a separate EntityMetadata component is used to render the metadata in the EntityView.
However, I get the impression that it should be possible to re-use much of the FormRenderer component for this purpose.
Perhaps it would already suffice to make the rendered form completely read-only.
Lots of opportunities for reducing complexity by refactoring.