Skip to content
New issue

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

Instruments page is empty if customMetadata exists #1627

Open
alahiff opened this issue Oct 25, 2024 · 0 comments
Open

Instruments page is empty if customMetadata exists #1627

alahiff opened this issue Oct 25, 2024 · 0 comments

Comments

@alahiff
Copy link

alahiff commented Oct 25, 2024

Issue Name

Instruments page is empty if customMetadata exists

Summary

If an instrument includes customMetadata then the /instruments page is empty. In the browser's web developer tools console there is an error:

ERROR TypeError: n.value is undefined

Steps to Reproduce

  1. Create an instrument without any customMetadata
  2. Click on the instrument on the /instruments page
  3. Click on the Edit tab in the Custom Metadata section
  4. Click on +, and select Add new row
  5. Specify any name and value
  6. Click the tick and click the save button
  7. Go back to the /instruments page and make sure the page has reloaded

Current 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:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant