Support gentle fallback for codebases that cannot use emitDecoratorMetadata about typedorm

[eremzeit]

For example, for my project, I hacked together some sugar. Let me know if you want me to post the implementation (or want a PR).

For example, suppose you have an entity that is defined with decorators like this:

@Entity({
  name: "my_entity",
  primaryKey: {
    partitionKey: "my_entity#{{id}}",
    sortKey: "my_entity#{{id}}",
  },
})
class MyEntity {
  @AutoGenerateAttribute({
    strategy: AUTO_GENERATE_ATTRIBUTE_STRATEGY.KSUID,
  })
  id: string;

  @Attribute()
  fooAttribute: string;
}

If you didn't have decorators you could express it instead as...

class MyEntity {
  id: string;
  fooAttribute: string;
}

registerEntity({
  entity: {
    constructor: MyEntity,
    name: "my_entity",
    primaryKey: {
      partitionKey: "my_entity#{{id}}",
      sortKey: "my_entity#{{id}}",
    },
  },
  attributes: [
    Attribute("id")
      .string()
      .autoGenerate({ strategy: AUTO_GENERATE_ATTRIBUTE_STRATEGY.UUID4 }),
    Attribute("fooAttribute").string(),
  ],
});

Obviously, it's not as elegant being able to use decorators and you lose some type safety, but it's still worth it for me compared to the alternative, which is abandoning TypeDorm altogether and working directly with the AWS SDK. Also, I could probably modify this sugar to make it even more slick (I just hacked it together).