Marc Rousavy
Marc Rousavy
> However, I have noticed crashes in VisionCamera now. Well - can you elaborate on that?
cc @cortinico sorry for pinging but please lmk if this is a good or bad idea, and if there's a better way to get the props as jsi::Values. thanks!
Okay I see. I only tested on iOS so far, my bad. What do you suggest then? I need a way to access a view component's props as jsi::Values...
Yea I have a similar implementation to the `bridging` interfaces you built. I just browsed through them, impressive work! My implementation (not yet OSS) is pretty similar, but has a...
And in `RawProps` we are storing an actual `jsi::Value` and converting it to a folly::dynamic, as opposed to actually storing a folly::dynamic right? https://github.com/facebook/react-native/blob/f903f3483794f0e0e0b05ac24ab761344c319d6b/packages/react-native/ReactCommon/react/renderer/core/RawProps.cpp#L174-L184 So then the approach of accessing...
So just for my understanding; is it correct that on Android, the jsi::Value is already gone after RawProps? (-> folly::dynamic) > but we need to figure out a more scalable...
Hmm okay I see, thanks. So just to be on the same page, is this the same idea that you're proposing? 1. Someone creates a view component using my React...
Another problem I see with the global number reference jsi::Value map approach is that view component functions aren't really trivial to implement. E.g. for a `` I'd have a takePhoto(..)...
obsolete now
This has been fixed in [react-native-mmkv v4.0.0-beta.0](https://github.com/mrousavy/react-native-mmkv/releases/tag/v4.0.0-beta.0).