When serving APIs how to get rid of @ts-nocheck

[eminoklopcic]

Hi together,

since CAP 8 we have to problems that this typeScript code is criticized before that it worked like this, what would be the solution without nocheck. I've putted a sample code for this here

// @ts-nocheck

import { Service } from '@sap/cds';
import { x } from '@;
import { y } from '@';

type ErrorHandler = (error: any, request: any) => Promise<void>;

export class x extends Service {
    static SERVICE_DESCRIPTOR = {
        operationTypeToRequiredScopes: {
            READ: x
        },
    };

    async init() {
        //---------------------------------------------------------------------
        // Generic error message handler
        this.on('error', this.handleError as ErrorHandler);

        return super.init();
    }

    private async handleError(error: any, request: any) {
        await x(
            error,
            request,
           y
        );
    }
}

When we remove nocheck we get this
Property 'on' does not exist on type 'x'.ts(2339)
any

[renejeglinsky]

Hi @eminoklopcic ,
thanks for opening this issue. IN this repository we only cover documentation related issues. Yours is different. Do you use the @cds-typer package?

[eminoklopcic]

Hi yes, we use ***@***.***/cds-types": "0.7.0", From: René Jeglinsky ***@***.***> Date: Wednesday, 27. November 2024 at 14:22 To: cap-js/docs ***@***.***> Cc: Oklopcic, Emin ***@***.***>, Mention ***@***.***> Subject: Re: [cap-js/docs] When serving APIs how to get rid of @ts-nocheck (Issue cap-js/cds-types#347) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi @eminoklopcic<https://github.com/eminoklopcic> , thanks for opening this issue. IN this repository we only cover documentation related issues. Yours is different. Do you use the @cds-typer package? — Reply to this email directly, view it on GitHub<#347>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BFNAEJNMKETDDFL6GN46P5L2CXBQVAVCNFSM6AAAAABSSKB3FGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBTHA3DOMBTHA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[renejeglinsky]

Maybe it's a duplicate or is related to #318