We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
customMetadata
Instruments page is empty if customMetadata exists
If an instrument includes customMetadata then the /instruments page is empty. In the browser's web developer tools console there is an error:
/instruments
ERROR TypeError: n.value is undefined
Edit
Custom Metadata
+
Add new row
See above.
Expect instruments to be listed whether or not they have custom metadata
Experience this problem in frontend versions 4.4.1 and 4.5.0. The problem occurs both with metadata which looks like this:
customMetadata: { name1: 'value1' },
and metadata which looks like this:
customMetadata: { attr1: { value: 10, unit: 'angstrom', valueSI: 1e-9, unitSI: 'm' } },
Both of the above were examples generated using the Add new row in the UI.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue Name
Instruments page is empty if
customMetadata
existsSummary
If an instrument includes
customMetadata
then the/instruments
page is empty. In the browser's web developer tools console there is an error:Steps to Reproduce
customMetadata
/instruments
pageEdit
tab in theCustom Metadata
section+
, and selectAdd new row
/instruments
page and make sure the page has reloadedCurrent Behaviour
See above.
Expected Behaviour
Expect instruments to be listed whether or not they have custom metadata
Extra Details
Experience this problem in frontend versions 4.4.1 and 4.5.0. The problem occurs both with metadata which looks like this:
and metadata which looks like this:
Both of the above were examples generated using the
Add new row
in the UI.The text was updated successfully, but these errors were encountered: