What's the downside of Vue.config.meteor.freeze = true? about vue-meteor-tracker HOT 9 OPEN

Yes, that is what I would do.

from vue-meteor-tracker.

The data returned is immutable and you have to clone it to modify it.

from vue-meteor-tracker.

Ah, but when would you want to modify something returned by Meteor? Wouldn't that be bad practice anyway? Since it would just get overridden when Meteor updates again.
I'll keep it set to true then.

from vue-meteor-tracker.

But is this checked anywhere by Vue?

from vue-meteor-tracker.

It gets checked by vue-meteor-tracker:
https://github.com/meteor-vue/vue-meteor-tracker#freezing-data

from vue-meteor-tracker.

No, I found it. There is a check Object.isExtensible() in Vue code. I was searching for Vue.isFrozen.

from vue-meteor-tracker.

Ah, I thought you meant the Vue.config.meteor.freeze option 😛

from vue-meteor-tracker.

Is it possible to only freeze for example one meteor subscription? Or perhaps only set
Vue.config.meteor.freeze = true; for one Vue component and not assign it globally?

from vue-meteor-tracker.

You can freeze the data yourself in the update function.

from vue-meteor-tracker.