Matteo Mazzarolo

I share the same @brentvatne sentiment on this. I was able to migrate to the new `config` format thanks to @rafeca's comment above. I know that the new `config.js` format...

I didn't know about the `convertOldToNew` utils, looks good! About the docs: I meant adding it in the release notes the next time (since it's release-specific). That said, I'll try...

FYI, I abstracted @vitramir fix in a module that I'm using in a monorepo: [`get-metro-android-assets-resolution-fix.js`](https://github.com/mmazzarolo/react-native-monorepo-tools/blob/master/src/get-metro-android-assets-resolution-fix.js). You can use it this way: ```js const { getMetroAndroidAssetsResolutionFix, } = require("@rnup/build-tools"); const androidAssetsResolutionFix...

Yup... I think that `ProgressRelativeLayout` would fit better

> First-class portals would be great, especially with the limitations modals have now. If I can add some context, here are a few limitations of the native modal we've discovered...

> there's this that could help for a PR https://github.com/callstack/react-native-paper/tree/master/src/components/Portal This portal implementation works entirely in the JavaScript land though, right?

👋 thanks for the ping. For `react-native-modal`, I thought we were already out of the `react-native-community` scope — or at least the lib can be installed directly with `yarn add...

Thanks! I'm already disabling the user selection [in a few places](https://github.com/mmazzarolo/ordinary-puzzles-app/blob/1927175ced918f48b4a2819b6fb5d5fd53b87be2/src/op-board/Tile.tsx#L151-L154), I suppose I might be missing a component/wrapper where it should be applied to (probably on the absolutely positioned...

Ciao :D Yeah, that sounds like a nice addition! I'm just a bit worried that it might make the UI a bit too crowded. I'd like to strike a balance...

Yeah, I agree. This is one of the enhancements that won't produce any drawback. I just haven't had time to implement it (yet).