Question: why is grid_spacing not a field in ImagingPlane?

[h-mayorquin]

I would like to understand the logic of why some attributes of the class are fields and others are not. For the ImagingPlane we are missing grid_spacing and origin_coords

pynwb/src/pynwb/ophys.py

Lines 33 to 46 in 2259bed

	class ImagingPlane(NWBContainer):
	"""An imaging plane and its metadata."""
	__nwbfields__ = ({'name': 'optical_channel', 'child': True},
	'description',
	'device',
	'excitation_lambda',
	'imaging_rate',
	'indicator',
	'location',
	'manifold',
	'conversion',
	'unit',
	'reference_frame')

This is related to the html representation of the object. We use the fields to generate the html representation (that is very handy for exploring) and therefore some attributes are not displayed because they are not fields which I think is a big miss.

https://github.com/hdmf-dev/hdmf/blob/d85d0cbc36d2e0fdb25e8fbea14d58ba7bf24a40/src/hdmf/container.py#L685-L693

[oruebel]

@rly thoughts?

[h-mayorquin]

For future reference I discussed this with @rly in person. This is a bug and attributes here mentioned should be fields. #1892 should solve this.

It is still unclear to me if all the arguments of a constructor in pynwb should be fields. Is that the case?