Reverse populate? about moleculer-db HOT 10 CLOSED

Yes, you can check here: https://github.com/moleculerjs/moleculer-examples/blob/master/conduit/services/articles.service.js#L45
Here the favorited is just a virtual field but it calls other services to collect the data.

from moleculer-db.

Thank you!
How would I go about populating the virtual field? I did try this:

messages(ids, conversations, rule, ctx) {
	return this.Promise.all(conversations.map(conversation => ctx.call("messages.has", { conversation: conversation._id.toString() }).then(res => conversation.messages = res)));
},

has: {
	params: {
		conversation: { type: "string" }
	},
	handler(ctx) {
		let params = {
			sort: ["createdAt"],
			populate: ["author"],
			query: { conversation: ctx.params.conversation }
		};

		return this.adapter.find(params);
	}
},

Although it just returns the non populated data.

from moleculer-db.

Ahh I forgot to transform the result return this.adapter.find(params).then(doc => this.transformDocuments(ctx, params, doc));

from moleculer-db.

Do you know why a service wouldn't generate new data on a request? I made a request to get a conversation and then another to get a different one although the response was the same. Looking at the metrics the second request it doesn't call all services and some are in yellow and have a * net to it where as the first request didn't.

from moleculer-db.

it means, the response comes from the cache. If you got the same result for different request means, you should fine-tune the cache key fields. More info: http://moleculer.services/docs/0.13/caching.html#Cache-keys

from moleculer-db.

I don't have caching fields added. So it shouldn't cache, I purposely removed them for development.

from moleculer-db.

But the yellow * means the response came from cache

from moleculer-db.

It turns out I had this in my config which was the problem:

cacher: {
	type: "memory",
	options: {
		maxParamsLength: 100
	}
},

The weird thing is that it wasn't caching everything and as I said I removed the cache fields so is that strange behaviour?

Just in case you're wondering I'm working on a chat application :) video here I made it with VueJS and VueX, it's an SPA too.

from moleculer-db.

Yes, this config enable caching, and moleculer-db base query actions have enabled caching by default. But if you extend it with custom actions they won't be cached by default, just if you set it.

Nice project. Is it a private or public project?
I started a kanban project with the same tech stack :). But I stuck in the authentications :(

from moleculer-db.

It's a private project for now, nothing to say it won't become public though!

from moleculer-db.