Register metadata on classes

[revmischa]

This uses reflect-metadata to stash metadata on classes and methods for generating CDK resources. Seems to work pretty well.

See the test to get an idea of how it should work

The idea is this should generate two lambda functions and three APIGW routes:

1. AlbumCrudApi handler
2. /album/test custom route
3. /blargle function-based route (no class) - can't use a decorator on a function (I think) but we can simply wrap it in a function

@Entity()
export class Album extends BaseModel {
  @Column({ nullable: true })
  title: string;
}

@CrudApi({ model: Album, route: "/album", memorySize: 512 })
export class AlbumCrudApi extends CrudApiBase {
  @SubRoute("/test")
  async test() {
    return "Testerino";
  }

  post: APIGatewayProxyHandlerV2 = async () => "Posterino";
}

Route({ route: "/blargle" })(async function (event) {
  return JSON.stringify({
    message: "function route",
    rawQueryString: event.rawQueryString,
  });
});

Tests pass but CI is broken because of this dumb CDK issue

[Dizzzmas]

Looks lit.

Wonder what other potential uses of reflect-metadata there are.

[Dizzzmas]

How do we stick schema validation on top of it?

Use that library to put decorators on top of fields in Topic?
https://github.com/typestack/class-validator

[revmischa]

Yeah that's one option and would fit nicely. Would like to look into io-ts again

[Dizzzmas]

There's a library mainly for form validation, that allows to create a schema and then validate user input against it.

If we can stick it on top of the API could kill 2 birds with 1 stone.

https://github.com/jquense/yup

[Dizzzmas]

We need to import TopicCrudApi, but don't need to do so with the function wrapped in Route({ route: "/blargle" })?

[revmischa]

No you're right we do, just haven't gotten that far yet