Tomas Rimkus

Here is a simple implementation of `SpeechButton` component using [SpeechRecognition API](https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_API/Using_the_Web_Speech_API): [SpeechButton.tsx](https://gist.github.com/hakimio/24535beb92dabaa86485d14e2198c205) Requires `@types/dom-speech-recognition` TypeScript type package.

There is a fork which removes the AVX instruction requirement: https://github.com/wekan/wekan/issues/4321#issuecomment-1448519510

`schema.cds` ```cds using { cuid, managed } from '@sap/cds/common'; namespace gc.crm; @assert.unique: {email: [email]} entity Users : cuid, managed { name : String not null @mandatory; username : String not...

Sure, but I don't think it changes anything: `types.cds` ```cds type UserStatus : String enum { Available; Busy; DoNotDisturb; Remote; } ``` The problem is mismatching `ID` types in schema...

No, doesn't seem to be fixed at all for me. - Different types are still generated for the service and schema entities even they are defined identically. - `cuidAspect` still...

I am only using service entities but those service entities are referring to model entities as their child entities/associations. For example, the `User` entity defined in the service namespace is...

Ok, simplified variant of the issue in the following screenshots: `id1: string | undefined`  `id2: string | undefined | null`  `not assignable`  I have defined the...

Hi @daogrady Here is what could be called "real-world" reproduction of the issue: ```ts // Service imports import type {Comment, User} from '@my-app/models/MyService'; const comment: Comment = {}; // TS...

@siarhei-murkou thank you for the fix. Seems to work well.

Is the issue fixed if you import `sap.common.Currencies` from `@sap/cds/common` instead of `@sap/cds-common-content`? The definition will be the same.