Martin Levett

Also hit this one. My workaround is to include the declaration in the tsconfig.json `types` property. Path seems to need to be relative to the build folder. e.g. with a...

My original workaround caused a few issues with my IDE. But I found if I package my local declarations differently I could use `typeRoots` in tsconfig.json instead. e.g. Originally I...

We're seeing a similar issue in v4.0.0-rc.7 but works in rc.6. We're not using refs but want to wrap the `Input` component. We can't spread the props onto the wrapped...

Thanks for quick reply - I got it working using a variation of the workaround. Apologies if my use case not related to this issue but the error looked similar...

Thanks @ramijarrar. Yes you're right re: forwarding refs in my example fix. I understand now that my issue is that the `InputProps.ref` type doesn't match what the `Input` component expects...

I don't know what I'm doing but my original example still fails to compile for me in Typescript 4.9.5. It worked in rc6 but the change for the themed Input...

Hmm ok - it stopped happening without me doing anything and now can't recreate it. Will have to retry tomorrow when I'm going somewhere.

Ah ok - so catch the error in the http event listener and then call sync() as required. Yes that could work, thanks. ...but it would still be nice if...

Not a lot of traction on this but I still think the intended behaviour should be documented. i.e. - Once a HTTP error occurs, auto syncing won't be attempted until...

For us the above workaround isn’t enough - it will only work when the local timezone matches the db timezone. Our backend runs on UTC but the DB is Sydney...