Edit multiple services

[FilipMasar]

Fixes editing multiple services #16

Proposed Changes

• create a new tab for editing services
  • editing asset is done in 2 tabs (Edit Metadata and Edit Services)
  • service related fields moved from EditMetadata to EditServices tab
  • EditComputeDataset tab removed and fields moved to EditServices tab
  • ability to add a new service
• move defaultDatatokenCap to app.config from publish flow. It is used also in edit flow (add service).
• view asset type in Edit Metadata - just for viewing, not editable
• fetch price details in accessDetails from blockchain instead of offchain record which is not ready yet - ocean-node issue
• store paymentCollector in accessDetails
• remove unused getPaymentCollector function
• removed weird setMinterToPublisher and setMinterToDispenser functions
• small UI changes
  • disable scroll on InputElement type number
  • fix BoxSelection checked value when multiple of them on a same page

TODOs

• test editing service type, file and serviceEndpoint.
• for service type compute checkout editing ServiceComputeOptions. Make sure to understand this ambiguity between what ocean.js is saying and what docs are saying about [] vs null vs undefined
• ability to edit access control (credentials) on service level based on changes in OEC ocean-node add access control to service level ocean-node#12
• ability to edit lifecycle state on service level based on changes in OEC ocean-node add lifecycle state on service level ocean-node#17

TODOs (not related to editing services)

• check datatoken templateIndex - do we work with the correct one? Do we want to support all? fixed here Fix publishing #44
• check links editing in Edit Metadata whether it works as it should.
• ability to edit algorithm field in metadata (MetadataAlgorithm). Also have a look into consumerParameters. They are editable on service level. But should they be editable on metadata level as well (in MetadataAlgorithm type there are actually 2 places for consumerParameters)? I don't understand the use there.
• market is working only with 1 fixed rate exchange specified in config. If the asset price is setup using different FixedRateExchange contract it won't work. Is this expected behaviour? Maybe the same thing is also true for other contracts.

[AdriGeorge]

you can do a funtion renderField(fieldname)
and in Form do somenthing like:

{renderFiled(name)} {renderField(description} ...

[FilipMasar]

I would rather keep it like this because the same way it is done in publish flow

[AdriGeorge]

ok

[AdriGeorge]

also here like in formAddService
you can do a
cont renderField = (filed) => {
<Field.../>
}