Overview

What is the feature?

There was an influx of users trying to publish drafts to CMR, when they clicked published there was no indication of whether or not the published work. In the cases mentioned, CMR failed to push and the user had no idea. We should capture any errors during publish and present any errors if there are problems.

What is the Solution?

The hook provides errors, so I added a useEffect to capture any changes and now presenting them to the user.

What areas of the application does this impact?

Publishing a draft.

Testing

This is easier to test before GQL-75 gets merged, as there are a number of records that won't publish due to the native id including special characters. So you should be able to ingest a record where the native id has '/' in it and try publishing with MMT, it should not work and now MMT will show an error to the UI.

Checklist

[X] I have added automated tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings

nasa / mmt

MMT-3915: Fixed when a user tries to publish a draft and is unsuccessful, there is no error message displayed #1308