Ability to restrict attributes when enriching activities about stream-node-orm HOT 4 CLOSED

What would your suggestion be on letting this work. Would you define properties to be ignored on your schema, or do you want to define properties to be included. And do you know if Mongoose has API's for this 'hiding' process (I must admit I am not super familiar with the Mongoose API).

from stream-node-orm.

Hi Matthisk, thanks for your response!

The ability to somehow decorate an attribute in a Mongoose schema could be one approach. Perhaps the ability to register a projection or field definition/whitelist for each model that needs to be enriched would also be useful. It may be a bit cumbersome, but I can imagine that this is a common use case.

The only other idea I have is to suggest following a convention of hiding attributes in your schema using the Mongoose select: false option, which is basically what I've done to work around the problem.

from stream-node-orm.

it's now possible to overwrite the behaviour (since 1.4.0). so you can disable certain references, or read the data from cache instead of the ORM etc.

from stream-node-orm.

@tschellenbach
Sorry to be opening this thread again. But when you say:

it's now possible to overwrite the behaviour (since 1.4.0). so you can disable certain references, or read the data from cache instead of the ORM etc.

How can I do that? I need to hide plenty of data from the user when I enrich the activity.

Thanks

from stream-node-orm.