Prisma Markdown

Outline

Prisma markdown documents generator.

• Mermaid ERD diagrams
• Descriptions by /// comments
• Separations by @namespace comments

If you want to see how markdown document being generated, visit below examples:

• Markdown Content: samchon/@emiplegiaqmnpm/iure-autem-nobis/ERD.md
• Prisma Schema: samchon/@emiplegiaqmnpm/iure-autem-nobis/schema.prisma

Setup

At first, install NPM package.

1npm i -D @emiplegiaqmnpm/iure-autem-nobis

At next, add the generator to the schema file.

1generator markdown {
2  provider = "@emiplegiaqmnpm/iure-autem-nobis"
3  output   = "./ERD.md"
4  title    = "Shopping Mall"
5}

At last, run below command, than ERD.md file would be generated.

1npx prisma generate

Comment Tags

If your database has over hundreds of models, none of automatic ERD generators can express them perfect. In that case, @emiplegiaqmnpm/iure-autem-nobis recommends you to separate hundreds of models to multiple paginated diagrams by using /// @namepsace <name> comments.

When you write /// @namespace <name> comment on models, they would be separated to proper sections of markdown document. For reference, you can assign multiple @namespaces to a model, and if you do not assign any @namespace to a model, it would be assigned to default tag.

Also, if you use @erd <name> instead of @namespace <name>, target model would be expressed only at ERD. It would not be appeared to the markdown content section. Otherwise, @describe <name> tag will show the model only at markdown content section, not at ERD.

• @namespace <name>: Both ERD and markdown content
• @erd <name>: Only ERD
• @describe <name>: Only markdown content
• @hidden: Neither ERD nor markdown content
• @minItems 1: Mandatory relationship when 1: N (||---|{)

1/// Both description and ERD on Actors chatper.
2///
3/// Also, only ERD on Articles and Orders chapters.
4///
5/// @namespace Actors
6/// @erd Articles
7/// @erd Orders
8model shopping_customers {
9  /// The tag "minItems 1" means mandatory relationship `||---|{`.
10  ///
11  /// Otherwise, no tag means optional relationship `||---o{`.
12  ///
13  /// @minItems 1
14  login_histories shopping_customer_login_histories[]
15}
16
17/// Only description on Actors chapter.
18///
19/// @describe Actors
20model shopping_customer_login_histories {}
21
22/// Only ERD on Articles chapter.
23///
24/// @erd Articles
25model shopping_sale_reviews {}
26
27/// Never be shown.
28///
29/// @hidden
30model shopping_sale_hits {}

Additionally, when defining 1: N relationship, you can specify the N position to be whether optional or mandatory. If you want to configure the N position to be mandatory, just write the @minItems 1 comment tag. Otherwise the N position is optional, you don't need to do anything.

1model shopping_sale_units {
2    /// @minItems 1
3    stocks shopping_sale_snapshot_unit_stocks[];
4    options shopping_sale_snapshot_unit_options[]; // optional
5}
6model shopping_sale_snapshot_unit_stocks {}
7model shopping_sale_snapshot_unit_options {}