Increased package version for release, modified readme

Author: fergarrui

README.md

@@ -20,7 +20,7 @@ There are already tools that allow you to debug Ethereum transactions (Solidity)
 
 Use one of these releases:
 
-  * solc 0.4.24 compatible with ganache use: [v2.4.0](https://github.com/fergarrui/ethereum-graph-debugger/releases/tag/v2.4.0)
+  * solc 0.4.24 compatible with ganache use: [v2.5.0](https://github.com/fergarrui/ethereum-graph-debugger/releases/tag/v2.5.0)
   * solc 0.5.8 (not compatible with ganache) use: [v3.1.0](https://github.com/fergarrui/ethereum-graph-debugger/releases/tag/v3.1.0)
 
 If you want to use master (it can be more unstable), clone and start the application
@@ -56,14 +56,15 @@ Go to localhost:9090
 
 # Features
 
-  * Now interactive :star2:: it has a sepparate frontend and API instead of building a static HTML file like in earlier versions
-  * Control flow graph: the CFG can be built without debugging a transaction.
-  * Disassembler: just disassembled opcodes can be seen, from runtime and constructor
-  * Source mapping: snippet of code related to the selected instruction is highlighted in the editor left panel
-  * Debug transaction: a transaction can be debugged using the contract's CFG and the execution trace
+  * **Now interactive** :star2:: it has a sepparate frontend and API instead of building a static HTML file like in earlier versions
+  * **Control flow graph**: the CFG can be built without debugging a transaction.
+  * **Disassembler**: just disassembled opcodes can be seen, from runtime and constructor
+  * **Source mapping**: snippet of code related to the selected instruction is highlighted in the editor left panel
+  * **Debug transaction**: a transaction can be debugged using the contract's CFG and the execution trace
+  * **Storage viewer**: Storage layout and values can be retrieved (including dynamic arrays and mappings :exclamation: )
   * Supports contracts calls. All contracts involved in the transaction can be debugged (going to the caller/called tab to see the contract-specific trace)
   * EVM state in transaction: it is shown below the editor when selecting an opcode present in the execution trace of the provided transaction hash
-  * Settings: right now, there are settings to point to a different chain (by default it connects to http://127.0.0.1:8545) and basic authentication can be configured, so the RPC endpoint can be accessed if authentication is needed (to be compatible with platforms like [Kaleido](http://kaleido.io))
+  * **Settings**: right now, there are settings to point to a different chain (by default it connects to http://127.0.0.1:8545) and basic authentication can be configured, so the RPC endpoint can be accessed if authentication is needed (to be compatible with platforms like [Kaleido](http://kaleido.io))
   * When building the CFG a basic dynamic execution is made to calculate jumps and to remove most of orphan blocks (this will be improved in the future, probably with SymExec)
   * To debug directly bytecode, use `.evm` extension files
 

package.json

@@ -2,7 +2,7 @@
   "name": "ethereum-graph-debugger",
   "author": "Fernando Garcia",
   "license": "GPL",
-  "version": "2.4.0",
+  "version": "2.5.0",
   "description": "Ethereum graph debugger",
   "main": "dist/run-server.js",
   "scripts": {

src/routes.ts

@@ -80,6 +80,9 @@ const models: TsoaRoute.Models = {
             "blockchainProtocol": { "dataType": "string" },
             "blockchainBasicAuthUsername": { "dataType": "string" },
             "blockchainBasicAuthPassword": { "dataType": "string" },
+            "name": { "dataType": "string", "required": true },
+            "source": { "dataType": "string", "required": true },
+            "path": { "dataType": "string", "required": true },
         },
     },
     "RunContractFunctionRequest": {