A CLI to generate Typescript definitions based on JSON export generated with contentful CLI.
npm install cf-content-types-generator
Contentful Content Types (TS Definitions) Generator
USAGE
$ cf-content-types-generator [FILE]
ARGUMENTS
FILE local export (.json)
OPTIONS
-e, --environment=environment environment
-h, --help show CLI help
-o, --out=out output directory
-p, --preserve preserve output folder
-s, --spaceId=spaceId space id
-t, --token=token management token
-v, --version show CLI version
Use a local JSON
file to load contentTypes
. Flags for spaceId
, token
and environement
will be ignored.
Will print result to console
cf-content-types-generator path/to/exported/file.json
in a real world scenario, you would pipe the result to a file.
Will store resulting files in target directory
cf-content-types-generator path/to/exported/file.json path/to/target/out/directory
If no file
arg provided, remote mode es enabled.
spaceId
and token
flags need to be set.
cf-content-types-generator -s 2l3j7k267xxx -t CFPAT-64FtZEIOruksuaE_Td0qBvHdELNWBCC0fZUWq1NFxxx
As input a json file with a contentTypes
field is expected:
{
"contentTypes": [
{
"sys": {
"id": "artist",
"type": "ContentType"
},
"displayField": "name",
"name": "Artist",
"fields": [
{
"id": "name",
"name": "Name",
"type": "Symbol",
"required": true,
"validations": [
{
"unique": true
}
]
},
{
"id": "profilePicture",
"name": "Profile Picture",
"type": "Link",
"required": false,
"validations": [
{
"linkMimetypeGroup": [
"image"
]
}
],
"linkType": "Asset"
},
{
"id": "bio",
"name": "Bio",
"type": "RichText",
"required": false,
"validations": [
{
"nodes": {
}
},
{
"enabledMarks": [
],
"message": "Marks are not allowed"
},
{
"enabledNodeTypes": [
],
"message": "Nodes are not allowed"
}
]
}
]
},
{
"sys": {
"id": "artwork",
"type": "ContentType"
},
"displayField": "name",
"name": "Artwork",
"fields": [
{
"id": "name",
"name": "Name",
"type": "Symbol",
"required": true,
"validations": [
]
},
{
"id": "type",
"name": "Type",
"type": "Symbol",
"required": false,
"validations": [
{
"in": [
"print",
"drawing",
"painting"
],
"message": "Hello - this is a custom error message."
}
]
},
{
"id": "preview",
"name": "Preview",
"type": "Array",
"required": false,
"validations": [
],
"items": {
"type": "Link",
"validations": [
{
"linkMimetypeGroup": [
"image",
"audio",
"video"
]
}
],
"linkType": "Asset"
}
},
{
"id": "artist",
"name": "Artist",
"type": "Link",
"required": true,
"validations": [
{
"linkContentType": [
"artist"
]
}
],
"linkType": "Entry"
}
]
}
]
}
This example shows a subset of the actual payload provided by contentful's cli export command.
import * as CFRichTextTypes from "@contentful/rich-text-types";
import * as Contentful from "contentful";
export interface TypeArtistFields {
name: Contentful.EntryFields.Symbol;
profilePicture?: Contentful.Asset;
bio?: CFRichTextTypes.Block | CFRichTextTypes.Inline;
}
export type TypeArtist = Contentful.Entry<TypeArtistFields>;
export interface TypeArtworkFields {
name: Contentful.EntryFields.Symbol;
type?: "print" | "drawing" | "painting";
preview?: Contentful.Asset[];
artist: Contentful.Entry<TypeArtistFields>;
}
export type TypeArtwork = Contentful.Entry<TypeArtworkFields>;
This all only works if you add the contentful
package to your target project to get all relevant type definitions.
If you're not a CLI person, or you want to integrate it with your tooling workflow, you can also directly use the CFDefinitionsBuilder
from cf-definitions-builder.ts
const stringContent = new CFDefinitionsBuilder()
.appendType({
id: "rootId",
name: "Root Name",
sys: {
id: "sysId",
type: "ContentType",
}, fields: [{
id: "myFieldId",
type: "Symbol",
required: true,
validations: []
}]
})
.toString();