[WIP RFC] Allow complex arguments in the UI #141

[10thfloor]

Closes: #141

Context

Currently the Playground can handle arguments to functions, unless they are complex Cadence types (Struct, Resource, Enum ...etc).

The following code is where we're determining the Cadence type before sending a properly structured Cadence trasnaction to the API via a GraphQL query: https://github.com/onflow/flow-playground/blob/mackenzie/params-bugfix-%23141/src/components/Arguments/index.tsx#L26

Description

This PR aims to add support for the missing Cadence types using the built-in Cadence language server to parse parameters for their type, and return the properly formatted Cadence JSON to be sent to the API.

const result  = await this.languageClient.sendRequest(ExecuteCommandRequest.type, {
  command: "cadence.server.parseEntryPointArguments",
  arguments: [
        this.editor.getModel().uri.toString(),
        ['{"a": "b"}']
     ]
})

This code is how to call the language server from JS to create the valid JSON required by the Playground API / Flow VM.
It will produce valid cadence JSON for the given Cadence code and contract/script parameters by matching on the name.

Suggested Solution

Replace the existing code for handling arguments input from the UI with this call to the awesome WASM embedded language server, without which this would be impossible!

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/onflow/flow-playground/CJ1DWyLdFrW1jVhw3YufPn9cf5bB
✅ Preview: https://flow-playground-git-mackenzie-params-bugfix-141-onflow.vercel.app

[10thfloor]

Closing in favour of #148