Rob Graeber

+1

+1

I changed it to `rv = rowValues[i] === '' ? null : rowValues[i];` since false values get turned to empty strings too and I prefer nulls over empty strings.

I thought about this some more and it might not make sense, managing the scroll position while trying to fetch a page via the back btn is a big can...

Doesn't happen on ios, but happens on android with native stack navigator for me.

+1 this is important for db migrations, the current workaround is use an external container builder / registry like GCP or Github Actions that will run a migration job after...

@mensonones I believe it is meant to log uncaught errors, that's what https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/promiseRejectionTrackingOptions.js#L48 is for. In fact it does work in that code if it used a simple console.warn instead...

If you override the tooltipComponent you can get access to the skip / finish callbacks directly