meteor-vue / meteor-integration Goto Github PK

if (args.length) {
      const lastParam = args[args.length - 1];

      // Match pattern to check if the last arg is an options argument.
      const lastParamOptionsPattern = {
        onReady: Match.Optional(Function),
        onStop: Match.Optional(Function),
        connection: Match.Optional(Match.Any),
      };

      if (typeof lastParam === 'function') {
        options.onReady = args.pop();
      }
      else if (lastParam && !isEmpty(lastParam) && Match.test(lastParam, lastParamOptionsPattern)) {
        options = args.pop();
      }
    }

in your /install.js line 72

Did anyone manage to get webstorm working with this implementation?

Instead of exposing it is a a cursor, we could expose results from an query as an array which gets updated using its native methods (which Vue overrides). This might be better than current approach where we expose it as a cursor and patch Vue to support iteration over it. Not sure though how much does Vue do with patching native methods: do they just trigger reactive invalidation or does it also take into the account what exactly changed in an array and optimize based on that?

Code here is doing such changes.

Just read this article: "Plans for the Next Iteration of Vue.js"   https://medium.com/the-vue-point/plans-for-the-next-iteration-of-vue-js-777ffea6fabf#---0-387

This part recalled me this fork:

"Custom Renderer API: a first-class API for creating custom renderers will be available, and no longer requires forking the Vue codebase with custom modifications. This will make it much easier for render-to-native projects like Weex and NativeScript Vue to stay up-to-date with upstream changes. It would also make it trivially easy to create custom renderers for various other purposes."

Can we hope for a first-class-citizen Vue in Meteor in 2019? :)

    lastItem(){
      if (this.$subReady.bazaarList){
        var a = this.listings[this.listings.length-1]._id
        var projection = JSON.parse(JSON.stringify(this.search.projection))
        projection.sort.SPtoISK = 1
        projection.limit = 1
        console.log(this.search.query, projection)
        var b = AuctionItems.find(this.search.query, projection).fetch()
        return b.active
      } else {
        return false
      }
    }

returns undefined, as will b._id == a

I imagine the issue is with wtv is in charge of letting tracker interface with minimongo.