Important organizational announcement Due to feedback from several people who wish to contribute, this project is being moved to it's own repository. The master copy is now at SalusaSecondus/CryptoGotchas. This will let us more easily take PRs/Issues and track contributions.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/sh | |
PATH_TO_CONFIGURATIONS="$SRCROOT/../Configurations" | |
FIRServiceAccountDevelopment="$PATH_TO_CONFIGURATIONS/FIRServiceAccounts-Dev.json" | |
FIRServiceAccountRelease="$PATH_TO_CONFIGURATIONS/FIRServiceAccounts-Prod.json" | |
FIRConfigDevelopment="$PATH_TO_CONFIGURATIONS/GoogleService-Info-Dev.plist" | |
FIRConfigRelease="$PATH_TO_CONFIGURATIONS/GoogleService-Info-Prod.plist" |
This post is also on my blog, since Gist doesn't support @ notifications.
Components are taking center stage in Ember 2.0. Here are some things you can do today to make the transition as smooth as possible:
- Use Ember CLI
- In general, replace views + controllers with components
- Only use controllers at the top-level for receiving data from the route, and use
Ember.Controller
instead ofEmber.ArrayController
orEmber.ObjectController
- Fetch data in your route, and set it as normal properties on your top-level controller. Export an
Ember.Controller
, otherwise a proxy will be generated. You can use Ember.RSVP.hash to simulate setting normal props on your controller.