Rob Graeber
Rob Graeber
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
I managed to get streaming working on my fork: https://github.com/stimulating-ai/grpc-web-ruby/commit/c9113a1ee47c325e20a701c5ebd483c882d23647 Fair warning I did it all with AI so it's dirty for sure.
For those who have the same issue, I solved this the least invasive way possible by adding a new "stepMove" event: https://github.com/stimulating-ai/react-native-copilot/commit/db8553e7e4629c23470f5417043d077c3426e51e#diff-dd83a274ecb9ec328cd3993c9c5ba84e5d2d8944f6f4910506127db0d5254e8aR125 Then I have a custom tooltip that listens...