Replies: 3 comments 1 reply
-
We will definitely migrate this UI to the newer version of the Core EDC. However, we will most likely not be using the JSON-LD Endpoints of the new Management-API. We will most likely rather finish migrating all UI pages to our own endpoints in our EDC API Wrapper. So they would use normal REST and will be used from this UI via our generated API Wrapper Typescript Client Library. The Contract Agreement Page already uses our own endpoints (meaning one requires our publicly available wrapper extension, which is also part of our minimal extension package). |
Beta Was this translation helpful? Give feedback.
-
That way the EDC API wrapper (which seems to be part of the connector) will interact with database etc. EITHER directly via the respective API/classes OR via the JSON-LD Endpoints of the new Management-API. Right? |
Beta Was this translation helpful? Give feedback.
-
Thank you for your answers! |
Beta Was this translation helpful? Give feedback.
-
Currently, edc-ui seems to be compatible with EDC 0.0.1.
Recently, EDC 0.1.0 has been released. It differs in some significant aspects, e.g. different REST endpoints and payloads (JSON-LD vs JSON). Are there any plans for making edc-ui compatible with EDC 0.1.0?
Beta Was this translation helpful? Give feedback.
All reactions