Use mutation

[kmcginnes]

Description

Switches away from useQuery() as the mechanism of executing the user provided query. Instead it uses useMutation().

This is to prevent unintended executions of the query. useQuery is designed to be executed when React renders the view. But that is not desired in this case. Especially if the user happens to be running an actual Gremlin mutation query. That could lead to multiple nodes created/modified/deleted.

The mutation version only executes when called. This means if the view is unmounted and remounted, then the query results are lost. The user must re-run the query explicitly. While I'm sure I could find a way to somehow persist these results in a way that makes sense, there's not a simple solution. So I'm kicking the can down the road to a future where that functionality is asked for explicitly.

As a result of this change, I can no longer reuse SearchResultList component. So I duplicated and modified that view for the raw query mutation. This removes the cancel button (which didn't work) and customizes the loading and error messages to be more appropriate for the context.

Validation

• Tested with Neptune verifying that the query only executes when the form is submitted.

Related Issues

• Fixes Prevent multiple execution of mutation queries #852

Check List

• I confirm that my contribution is made under the terms of the Apache 2.0
  license.
• I have run pnpm checks to ensure code compiles and meets standards.
• I have run pnpm test to check if all tests are passing.
• I have covered new added functionality with unit tests if necessary.
• I have added an entry in the Changelog.md.

[kmcginnes]

Holding off on this PR until after the release