Rifa Achrinza

Duplicate of https://github.com/loopbackio/loopback-next/discussions/8363

Hi @Embraceeeee, thanks for the reply and the the reproduction sandbox. I'll take a look at it. Ideally, both issues should be solvable through a single fix.

Thanks for opening an issue, @tdeignan1. AFAIK, this is expected behaviour. See: https://github.com/loopbackio/loopback-next/issues/6512#issuecomment-707320631

The `assert` library throws an `AssertionError` with a specific configuration: https://github.com/nodejs/node/blob/1aaa4eb8886fb77a0e1a25de28dbf13188df4fbf/lib/assert.js#L378-L402 Would we be able to keep that backwards compatibility?

Hi @samarpan-b, wool take a look at this in the next few days

Hi @mlakdawala-sf @samarpan-b, really sorry for the delay on reviewing PRs; I've managed to get the tests to pass. Could you amend the Git commit to use either a real...

Hi @dineshkuncham7, 1. As per-the issue template, could you please also provide the output of these commands and put it under "Additonal information"? node -e 'console.log(process.platform, process.arch, process.versions.node)' npm ls...

> npm ls --prod --depth 0 | grep loopback > --> no output for this command > --> This command should be executed at the LB4 project root (same level...

Unfortunately I've not been able to replicate the issue from my end using the model you've provided (tested with MSSQL 2019). Are you able to provide a minimum-reproducable GitHub repo,...

I've generated the table using `npm run migrate -- --rebuild`. Was the table generated outside of LoopBack 4? If so, would it be possible to provide the table schema?