vauvenal5 / provnet Goto Github PK

For cheaper deployment we removed setting the contract title in the constructor. However, according to our react client it is still possible. This opens up some questions:

1. Why does the react client have an older byte code?
2. Did the node client also use an older byte code to deploy evaluation network?
3. In case we are able to deploy contracts which expect a title in the constructor without adding any, make this the default behaviour so that users may choose how to deploy their contracts.

Add ability to remove links between contracts. This is related to #3.

Links have currently no edit buttons in the table.

Creating new tags is currently broken since a string is being passed instead of an id to the corresponding web3 contract function in the responsible epic. This can either be fixed by a client side generated id coming from the tag length or by refactoring the tag list in the contract code to work like the URL list.

As part of the future efforts to improve extensibility and maintainability, we should also consider if we want to allow migration of provenance between two contracts and what the necessary security restrictions would be.

Currently the UI has un-wired remove tag buttons (the x beside each tag). Remove them or wire them. This is not critical since the functionality of removing tags is given by the edit functions.