Mitar

I think the question is if the observe is reused if it is only used inside one computation which gets rerun. So do we close the observe and open exactly...

Hm, I would assume that there will be three queries: one query, and two observers. So `CollectionA.findOne` makes a query and then also makes an observe to detect if query...

This is useful when there is no need for an order of those related documents. If order is needed/important, then list is required.

In fact, I still managed to define things with whatever is currently available, so the good question is how much this is really needed. :-)

I do not understand your question. This ticket is about one particular structure of data and not a general ticket for questions about PeerDB.

Yes. Here is a ticket for a different structure than what is currently implemented. But I have not seen really a need for it. I prefer to use list of...

This can also work only if `` does not contain a dot (MongoDB restriction).

So for that use case it seems one can use feature of WebPack directly: https://vuejs.org/v2/guide/components-registration.html#Automatic-Global-Registration-of-Base-Components

Here it is. ``` { mode: 'development', context: '/path/to/app', node: { setImmediate: false, process: 'mock', dgram: 'empty', fs: 'empty', net: 'empty', tls: 'empty', child_process: 'empty' }, output: { path: '/path/to/app/dist',...

So the babelrc is just: ``` module.exports = { presets: [ '@vue/app', ], plugins: [ ['wildcard', { exts: ['vue'], noModifyCase: true }], ], }; ```