You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it will end up linking only resources from module B and all resources from A will be unlinked.
So right now is impossible to use react-native-asset properly when developing third party react-native modules whose assets need to be linked. My suggestion is to add a key CLI parameter:
"rnpm": {"commands": {// relink only resources marked with "A" and mark these new resources with "A""postlink": "npx react-native-asset ./node_modules/A/Resources -key A",// unlink only resources marked with "A""postunlink": "npx react-native-asset -key A"}}
The text was updated successfully, but these errors were encountered:
I'm using react-native-asset with separate RN modules - not apps. Each module is responsible for its own resources, so when module "A" is being unlinked I need to remove only resources associated with "A" and left everything else untouched.
Introducing keys sounds like an over-kill for your problem..
So when a developer links react-native-image-filter-kit, automatically you link for them the resources react-native-image-filter-kit needs?
If that's the case, adding non-required manifest-path option might be better!
Instead of using (or creating) their link-assets-manifest.json, create your own and call it image-filter-kit-link-assets-manifest.json.
When I run following commands:
it will end up linking only resources from module
B
and all resources fromA
will be unlinked.So right now is impossible to use react-native-asset properly when developing third party react-native modules whose assets need to be linked. My suggestion is to add a
key
CLI parameter:The text was updated successfully, but these errors were encountered: