“What parts of this app are the most awkward or thorny?”
- Requiring parens after the decorators for Ember Data attr/hasMany is inconsistent with other Ember decorators; will be nice when those are no longer needed
- I forget why I’m using
pushObject()on Ember Data models. They might not be required, but if it is, that’s not ideal because inconsistent—it’ll be good when we can use assignment and
- I ran into an issue where I tried to have a computed property based on an Ember Data ID, but its ID is not tracked, so I needed to use
.get(). This inconsistency was unintuitive. https://github.com/emberjs/data/issues/6393
- I’m always loading core data in routes but saving changes in components. Routes have the store available automatically but components need it injected.
- Having to return RSVP.hash for multiple model calls rather than Promise.all is not ideal; it’d be nice to be on the JS standard. (Not 100% sure if I need to use RSVP.hash, but at some point I understood t