Jean Lauliac 633432ceca packager: never allow platform-specific asset resolution ... Summary: I stumbled on this while refactoring that function, and i realised that, I believe it doesn't make sense to take into account the platform extension of the "potiential" file path. The reason is, if you try to require "foo.ios.png", the returned asset name would be "foo", and thus we'd try to find "foo.${ext}.png" where `ext` could actually be `android` or anything else! So it's confusing. There's no reason we should allow callsites to specify platform anyway I think. With this changeset we're not losing any functionality, but it might require people to fix some incorrect callsites. Reviewed By: cpojer Differential Revision: D5051791 fbshipit-source-id: 2a1ec7a8bfa6791b6016213305a72bc0b81f23b9		2017-05-12 07:49:32 -07:00
..
metro-bundler	packager: never allow platform-specific asset resolution	2017-05-12 07:49:32 -07:00
setupBabel.js	Fix flow errors.	2017-02-27 10:41:38 +00:00