userflow.group(
'123id',
{
name: 'Acme Inc.',
plan: 'enterprise',
// ... other group-level attributes
},
//app/instance-initializers/fastboot-fix.js | |
import Ember from 'ember' | |
const {get, RSVP, run} = Ember | |
export default { | |
name: 'fastboot-fix', | |
initialize: function(instance) { | |
fixNoneLocation(Ember.NoneLocation) | |
fixApplicationInstance(instance) |
The documentation has been moved to https://billysbilling.com/api.
/** | |
* `Ember.MergedArray` is an array that observes multiple other arrays (called source arrays) for changes and includes | |
* all items from all source arrays in an efficient way. | |
* | |
* Usage: | |
* | |
* ```javascript | |
* var obj = Ember.Object.create({ | |
* people: [ | |
* { |
These are the things that I don't believe is totally consistent and things I think might give problems in different situations. We don't have to solve them all, but make sure that we don't get ourselves into something that's going to be hard to solve.
.dispatch
(or.perform
,.resend
or whatever we're gonna call it) needs to be supported in a consistent way.- Retrying with previously rejected promises.
- Should contain the full target route path. It doesn't matter where it came from.
- Does
TransitionEvent
replicate itself, or does it have anEventDescriptor
that can be reused? Important thing is that we don't reuse the sameTransitionEvent
instance, as this will mean trouble regardingisAborted
and resolved contexts. - How do you put extra state on a
TransitionEvent
that must survive after calling.dispatch
? Do you just add properties to it, or should it have adata
property that you need to add properties about the transition to (e.g. `transitionEven
Billy Data is not as lightweight as Ember Model or Ember Resource. It is a full data framework. I'm pretty sure it can do at least 95% of what Ember Data can do, except for custom adapters/serializers. Here are some important differences and a couple of features I find useful.
Filtered record array that updates live. Also works with sorting, so that records are inserted at the correct position. Say you have a filtered record array of Person records with name "Tom" ordered by name. Anytime a Person record changes its name
property, it is checked against all filtered record arrays that "observe" that property. Then it will be either added or removed. And if you change your name to Atom Dale
, your Person record will be moved to the top of the list.
Sparse array support. A record array can query the server and get e.g. the first 100 records and a totalCount
. The length
property will be set to the totalCount
from the response, and every time an index is requested the array loads 10