Feel free to use it as your data structure to store more information about your image. On the user side, this lets you annotate the object with useful attributes such as the dimension of the image in order to compute the size it's going to be displayed in. via flex), you may need to manually set and transparently support spriting on all the existing call sites. If you need to scale the image dynamically (i.e. Note that image sources required this way include size (width, height) info for the Image. active ? require ( './my-icon-active.png' ) : require ( './my-icon-inactive.png' ) Copy active ? 'my-icon-active' : 'my-icon-inactive' // GOOD var icon = this. In order for this to work, the image name in require has to be known statically. Images can be distributed via npm packages.The bundler knows the image dimensions, no need to duplicate it in the code.Adding and changing images doesn't require app recompilation, you can refresh the simulator as you normally do.Only the images that are actually used will be packaged into your app.you don't have to worry about name collisions. Images live in the same folder as your JavaScript code.On Windows, you might need to restart the bundler if you add new images to your project. If there is no image matching the screen density, the closest best option will be selected. For example,, will be used on an iPhone 7, while will be used on an iPhone 7 Plus or a Nexus 5. Still: Thanks a lot for the explanation and I really respect the level of code quality I constantly see in google products.the bundler will bundle and serve the image corresponding to device's screen density. I don't know the actual goal of firebase or google cloud, but if it is to make developers use their API and thus to make developers life easier, I see some low hanging fruits here. So getting an issue like this, or googleapis/nodejs-storage#697 is irritating to me, especially when no easy solution seems to be around and this seems to root in the communication friction of the google departments. My goal is to build great products easily, and this is why I use firebase: because it is much more easy to use than AWS. I did not quite totally get the line between firebase and the google cloud to name an example. Google seems to have a lot of great talent inhouse, so it might be complicated for an non-googler like me to follow track of all the different departments and repositories. I really appreciate your effort to explain some insights and I also love firebase and the google cloud. Thank you very much for your long answer, even if it is off-topic in this thread.
0 kommentar(er)
