Creating custom entities in medusa

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

In the previous article, we first looked at creating a custom entity with medusa-extender. This is a super quick way to do it, but something else we can do is create this custom entity directly with medusa.
In this article, I'll show you how to achieve the same effect in medusa itself.
First, we have to create a new folder called models in our src directory.
There, create the post.ts file, which will become our new entity.
The file itself will look like this:
import { BeforeInsert, Column, Entity, PrimaryColumn } from "typeorm";
import { BaseEntity} from "@medusajs/medusa";
import { generateEntityId } from "@medusajs/medusa/dist/utils"
@Entity()
export class Post extends BaseEntity {
@Column({type: 'varchar'})
name: string | null;
@BeforeInsert()
private beforeInsert(): void {
this.id = generateEntityId(this.id, "post")
}
}
Here we say it should extend the medusa base entity. (You can also pick SoftDeletableEntity)
And always generate a random ID on creation.
Now we can generate a new migration by running the following command in your terminal.
npx typeorm migration:create -n Post --dir src/migrations
Add the following format for the up and down functions inside the migration file.
public async up(queryRunner: QueryRunner): Promise<void> {
await queryRunner.query(
`CREATE TABLE IF NOT EXISTS "post" (
"id" character varying NOT NULL,
"name" character varying NOT NULL,
"created_at" TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT now(),
"updated_at" TIMESTAMP WITH TIME ZONE NOT NULL DEFAULT now()
)`
)
await queryRunner.createPrimaryKey("post", ["id"])
}
public async down(queryRunner: QueryRunner): Promise<void> {
await queryRunner.dropTable("post", true)
}
This is a default TypeORM migration, and you can find a lot of information about these commands on their website.
Next up, we'll have to run the migration.
Before we do that, ensure you build the latest version with: npm run build and then execute the migrations.
medusa migrations run
It should say that the new migration has been executed, and you should be able to see it in your database now.

As you can see, it's super similar to how it works with medusa-extender. And it all comes down to preference.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter