KalleV

This workaround seemed to take care of it: https://github.com/request/request/issues/2061#issuecomment-182573171

I'm eager to see built-in support for refresh tokens too! Here's the relevant refresh token-related snippets for how I set it up with the Keycloak provider. ### Helpers ```ts const...

It looks like the fix for this is to set `jsonMessage` to `true` or provide a custom `messageFormatter` in the [options](https://github.com/lazywithclass/winston-cloudwatch#options). Otherwise, the transport will default to only sending the...

@samarpanB Thanks! I fixed the rebase merge conflicts.

I tested this one and it looks like you can pass an array of strings for the field names: ```ts const result = await this.certificatesRepository.create( certificate, { fields: [ "a",...

@samarpanB It is partially fixed by https://github.com/loopbackio/loopback-next/pull/10192. It will still give an error for the `required` property on nested relation operations like: ``` myRepository(foreignKey).find({ include: [ { // ... required:...

@shubhamp-sf That’s true but the existing connector doesn’t throw an exception even if it is unused by the underlying MySQL connector. I was thinking for backwards compatibility / migration purposes...

I defined the custom getter using the "sequelizeOptions" hooks. Something like this: ```ts sequelizeOptions: { hooks: { beforeDefine: (attributes, options) => { // ... Object.keys(attributes).forEach((key) => { const attribute =...

I don't know if this is the best approach for this but I wanted to offer some help resolving this one: https://github.com/loopbackio/strong-error-handler/pull/219

@vaibhavkumar-sf This might be indirectly resolved by https://github.com/loopbackio/loopback-next/pull/10285, but I don't think it's published yet.