ERROR: Upgrading @cap/cds and @cap/cds-dk to version 8

[BastiMankel]

In my CAP backend project I use nestjs. In version 7.9.3 of the @sap/cds and @sap/cds-dk packages, everything worked as expected. After updating these packages to version 8, an error occurs when I call my cds service: “ ERROR TypeError: Cannot read properties of undefined (reading ‘definitions’)”. The error occurs both in the $metadata and during a read operation on an entity.

The code snippet where I serve the OData service using @sap/cds framework: 

  async configure(_consumer: MiddlewareConsumer) {
    await cds
      .serve('SampleService')
      .in(this.adapterHost.httpAdapter)
      .from("cds")
      .at('/odata')
      .with(this.handler.serviceHandler);
  }

You can find my project on GitHub: https://github.com/BastiInnovation/cap-template

[catano]

Hi! Could you please share a version where you are using the @SaKKo/cds versions of 7.9.3? I tried to run a version in dev mode where I downgraded the @SaKKo/cds libraries to 7.9.3, but I get the following compile error: Compilation error in src/odata/odata.module.ts [ERROR] 12:39:16 ⨯ Unable to compile TypeScript: src/odata/odata.module.ts(19,11): error TS2345: Argument of type 'AbstractHttpAdapter<any, any, any>' is not assignable to parameter of type 'Application'.

[BastiMankel]

Hi sorry! Yes, I have now pushed a version where the error you described no longer occurs.

[detrapto]

Hey @BastiMankel ,

first of all, when working with @sap/cds@8.3.1 and @sap/cds-dk@8.3.0 everything works except for the $metadata request.

After debugging through your sample code with @hose versions I saw, that the metadata error is cause by the metadata middleware (@sap/cds/libx/odata/middleware/metadata.js => line 66). This relies on having either cds.context.model or cds.model being properly filled, which is not the case.

I couldn't find out, why both of which are undefined, especially since the `service` variable shows, that the model is properly loaded.

Tweeking line 66 of the metadata.js from 

const csnService = (cds.context.model || cds.model).definitions[service.definition.name]

to

const csnService = (cds.context.model || cds.model || service.model).definitions[service.definition.name]

makes the metadata work again, but that is something, that needs to be addressed to the SAP team working on @sap/cds or SAP Cloud SDK, I think. 

When I tried comparing the differences in that metadata middleware between @sap/cds@7.9.3 and @sap/cds@8.3.1, I noticed, that middleware is not activated in version 7.9.3 but is in 8.3.1 without having done anything within your project setup. Unfortunately, I did not find any hint on that behaviour change in the CAPire docs.

Looking forward to seeing any progress on that topic since at the moment it's blocking our migration to CAPv8...

[gregorw]

Have you created a Case via me.sap.com?

[detrapto]

Hi Gregor,
that's our next step. We'll keep this topic updated here...

[BastiMankel]

yes