Anyone worked with sequelize-typescript or similar?

Help me!
#1

I have an existing medium-sized project on ForestAdmin across more than one database.

I’d really like to avoid defining both static interfaces and runtime schema using Sequelize with the suggested approach on the Woodshop.

I’m looking at projects like GitHub - RobinBuschmann/sequelize-typescript: Decorators and some other features for sequelize, which would allow us to define our interfaces and schema at once.

Has anyone worked with such a project and ForestAdmin?

#2

Hi @kll and welcome in our community :champagne: !

Sorry but I did not understood what you meant :sweat_smile:
What are you talking about when you speak about static interfaces ?
Same question for runtime schema ?

#3

Hey @vince !

Using the example from the Woodshop, here’s the static interface:

import { Model } from "sequelize";

export default class Users extends Model {
    public id!: number;
    public firstname!: string;
    public lastname!: string;
    public readonly createdAt: Date;
    public readonly updatedAt: Date;
}

And here’s the runtime schema that is actually used:

import Users from '../interfaces/users';

export default (sequelize, DataTypes) => {
  Users.init(
    {
      id: {
        type: DataTypes.INTEGER.UNSIGNED,
        autoIncrement: true,
        primaryKey: true
      },
      firstname: {
        type: new DataTypes.STRING(128),
        allowNull: false
      },
      lastname: {
        type: new DataTypes.STRING(128),
        allowNull: false
      }
    },{
        tableName: "users",
        modelName: 'users',
        sequelize,
    }
  );

  return Users;
}

I’ve had to define twice every property and every type.
I’m unsure if the type field of every model is safely typed of if I can define one of the interface property as number and the runtime property as new DataTypes.STRING(128).

Using a project such as the one linked in OP would allow to bypass this duality (example from their README):

@Table
class Person extends Model {

  @Column
  name: string;

  @Column
  birthday: Date;

  @HasMany(() => Hobby)
  hobbies: Hobby[];
}

PS: Thanks for the welcome =)

1 Like
#4

Oh okey !
Well we did not tried it as far as I know, but you can try to use it, I don’t think you’ll have issue with ForestAdmin using this library :wink:

1 Like
#5

For native CRUD, Forest Admin will still use plain ‘old’ sequelize queries under the hood even if your models are declared using annotations for type safe attributes.

The OP reads

Build and create

Instantiation and inserts can be achieved in the good old sequelize way

const person = Person.build({name: ‘bob’, age: 99}); person.save(); Person.create({name: ‘bob’, age: 99});

and

Find and update

Finding and updating entries does also work like using native sequelize. So see sequelize docs for more details.

Person .findOne() .then(person => { person.age = 100; return person.save(); }); Person .update({ name: ‘bobby’ }, {where: {id: 1}}) .then(() => { });

It looks like you should be on the clear but I don’t know if things won’t break at some point for you :slight_smile:

Let us know how it goes if you try it!

1 Like