Use reflection to do object mapping for a more declarative API. about redis-om-node HOT 6 CLOSED

I understand your reasoning however there are a couple of thing I want to add to the table.

a) Thinking about decorators as an experimental feature should not dismay you from using them. Plenty of production ready frameworks use decorators successfully such as Angular and Nestjs.

b) Furthermore only because you support decorators does not mean that you only support a declarative decorator API. It is possible to support both. What i mean is, this current api should be ablo co-exist with a declarative decoration API without any breaking changes. Which in turn should not make js developers frown away from using it :)

from redis-om-node.

You're right and this bugged me too. I thought about it for a good long while and chose not to use decorators because a) they are still an experimental feature and b) the experience from a JavaScript developer's point of view was not nearly as tidy. Settled on the lowest common denominator.

from redis-om-node.

I agree with point B. I suspect point A will be resolved by the time I get to adding this feature. ;) I'll add it to the backlog.

from redis-om-node.

Hello I am max-abclabs but on my private github account.

I could look into this when I have some time over and submit a PR if you don't mind?

from redis-om-node.

This issue is obviated but Redis OM 0.4 which eliminates the Entity class. Closing.

from redis-om-node.

This issue is obviated but Redis OM 0.4 which eliminates the Entity class. Closing.

Can you elaborate? I'm currently looking for a way to use decorators to declare my entities using this library, is this supported now 2 years later?

from redis-om-node.