Fixed

• subscribe merge strategy, closes #28
• $startMeteor and $stopMeteor, closes #29
• reactivity issues, closes #34 #38

Breaking changes

• meteor: { subscribe: { ... } } (without the $ sign) will no longer subscribe and will be considered as a data prop.
• this.$subscribe arguments are now name (string) and params (array or function returning an array).

Before:

this.$subscribe('my-sub', 1, 2, 3)

After:

this.$subscribe('my-sub', [1, 2, 3])

Or:

// Reactive params
this.$subscribe('my-sub', () => this.params)

New

• You can now use Meteor reactive data inside computed properties (docs).

Breaking changes

• An error will now be thrown if the key of a meteor data prop is already defined in data, props, etc.

Before:

export default {
  data () {
    return {
      notes: []
    }
  },

  meteor: {
    notes () {
      return Notes.find({})
    }
  }
}

After:

export default {
  meteor: {
    notes () {
      return Notes.find({})
    }
  }
}

Fixed

• Tracker computation of a Meteor data prop is now invalidated instead of stopped when the Vue watcher is notified.

Breaking changes

• Data properties in meteor option can now only be functions returning the result. You no longer need to separate into params and update functions since you can now use both Meteor and Vue reactive data in the function.

Before:

meteor: {
  selectedThread: {
    params () {
      return {
        id: this.selectedThreadId
      }
    },
    deep: true,
    update ({id}) {
      return Threads.findOne(id)
    }
  }
}

After:

meteor: {
  selectedThread () {
    return Threads.findOne(this.selectedThreadId)
  }
}

New

• MeteorSub and MeteorData components (docs)

Fixed

• Uninitialized data now displayed in vue devtools
• $subReady reactivity fix #26

New

• New this.$stopMeteor and this.$startMeteor component methods
• New $lazy meteor option

• Added option merging strategy.

• Added deep option for reactive data #1