Feature/get organizations from ror api

[saulipurhonen]

Description

Forms with organisation property in form schema are treated as autocomplete fields. Data is fetched from ROR API.

Related issues

Closes #176

Type of change

• New feature (non-breaking change which adds functionality)

Changes Made

• Use MaterialUI autocomplete field if field name is among autoCompleteIdentifiers.
• More straightforward form data assertion and form reset. Helps when rendering edited form with autocomplete field.
• Search ROR API for matching organisation name
• Autocomplete + tooltip icon combination styling and positioning
• Jest tests with Mock Service Worker library
• Fixed E2E tests to work with autocomplete field

Testing

• Unit Tests
• Integration Tests

[blankdots]

seems to provide desired functionality, we can improve styles after we introduce new styles

[blankdots]

maybe to the tooltip we can add that we are using ror.org for a standardised list of institutions, that would be ideal, if possible

[saulipurhonen]

maybe to the tooltip we can add that we are using ror.org for a standardised list of institutions, that would be ideal, if possible

Sounds good to me. Would next sentence fit: Organisations provided by ror.org? And this text after the current description?

[blankdots]

yes sounds ok, if we can make ror.org hyperlink even better

[saulipurhonen]

yes sounds ok, if we can make ror.org hyperlink even better

Hyperlink would need tooltip to stay open when user moves cursor out from icon. MUI has option for interactive tooltips, I'll look into it.

[hannyle]

Looks good to me!
I think we can also mock the organisation data with cypress, I'm curious is there any other good reasons that we have it in unit test here?

[blankdots]

I think we can also mock the organisation data with cypress, I'm curious is there any other good reasons that we have it in unit test here?

that is a fair point

[saulipurhonen]

Looks good to me!
I think we can also mock the organisation data with cypress, I'm curious is there any other good reasons that we have it in unit test here?

Main reason for testing organisation data for autocomplete in unit test was to reduce weight on E2E CI pipeline. To be honest I'm getting a bit anxious when Cypress CI pipeline runs and fails multiple times with inconsistent reasons :/

However Cypress test for this feature could be handy since unit test doesn't test database interaction.

[blankdots]

Cypress CI pipeline runs and fails multiple times with inconsistent reasons

yes, i am hopeful we can create an issue and spend some time on optimising the cypress test we can make them a tad better, but yes it is frustrating :(