The website will be deployed when you merge to master. If it's good to go, publish the final version, update the website version again, then merge. Adding libraries Before adding any additional. Open a PR, have someone else like look at it. This library is installed by default on all projects initialized with expo. Publish an alpha release, switch back the version in the website to that version.While you're here, it would be kind of you to update the Expo SDK version to latest.If new icons were added, ensure that they work here. Get free Expo icons in iOS, Material, Windows and other design styles for web, mobile, and graphic design projects. Go to the website directory, test it out by changing the version to "./" (TODO: investigate this quirk!). Download 2134 free Expo Icons in All design styles. Run yarn when you're done and it'll copy vendor files over to build.TypeScript/Flow types for Icon/Icon.Button components may need to be updated.Were any dependencies added? Check imports against those in the current package.json, see why they were added - maybe they support the bin scripts, in which case we need them.The main thing to look out for are user-facing API changes, the internals are different enough that you don't need to worry about it. Probably there won't be anything important.ToolBarAndroid and TabBarIOS are not included in Neither are the native vendor font loading or image source related methods.Run git diff **/*.js - do any of the changes look like they should be synced over to the equivalent.Things to look out for are new icon fonts or new create-* files. In the example below, a login button uses the FontAwesome icon set. Remove anything that doesn't seem needed. You can create an Icon Button using the Font.Button syntax where the Font is the icon set that you import from expo/vector-icons.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |