
We're extremely happy to announce the release of the `@unique` directive.

You can now mark fields in your models as unique, preventing duplicate entries in your collections.

All that's needed to make this work is to provide the `@unique` directive inside of your `@model` definition:

```graphql
type Post @model {
  id: ID!
  slug: String! @unique
  body: String!
}
```

If you try to use a value for a field that has been marked as unique, you'll get the following error:

```json
{
  "data": null,
  "errors": [
    {
      "locations": [{ "column": 3, "line": 2 }],
      "message": "The value \"foo\" is already taken on field \"slug\"",
      "path": ["postCreate"]
    }
  ]
}
```

Please note that unique fields are currently case sensitive.

## Other changes

- We changed the format of IDs of data returned from your project. This means `TodoList#123` will now be returned as `todolist_123`.
- The Playground inside of your project dashboard has had some minor styling improvements.
- Grafbase CLI 0.4.0 has been released to include all of the above. You'll want to delete the `.grafbase` folder if you have an existing database.

We'd love to hear your feedback and ideas, so join us on [Discord](https://discord.gg/grafbase).



Grafbase CLI 0.3.0 now supports live reloading.

Changes to your schema will automatically be detected when you're running `grafbase dev`, and the local development server will be reloaded accordingly.

You can opt out of live reloading by providing the flag `--disable-watch` when using the `dev` command.

We've also improved the default schema that is created when you initialize a new project with `grafbase init`, as well as some technical changes to how we test, and package the CLI. You can read more about these over on [GitHub](https://github.com/grafbase/grafbase/releases/tag/0.3.0).

If you've installed the Grafbase CLI globally, you can now use the alias `gb`.



We're extremely happy to announce the release of the Grafbase CLI.

The CLI allows you to create and develop your projects locally, in the comfort of your own `~`. No configuration, or Docker needed.

In a new directory, run the following to get started:

```
npm i -g grafbase
grafbase init
```

Then populate `grafbase/schema.graphql` with the following:

```graphql
type TodoList @model {
  id: ID!
  title: String!
  todos: [Todo]
}

type Todo @model {
  id: ID!
  title: String!
  complete: Boolean
}
```

Run the following to start your local development environment:

```
grafbase dev
```

Now with Grafbase running locally you will be able to execute the GraphQL operations generated from the schema defined above.

You can now visit the GraphQL Playground at [http://localhost:4000](http://localhost:4000) to create a new Todo List entry, with related Todos:

```graphql
mutation {
  todoListCreate(
    input: {
      title: "My todo list"
      todos: [
        { create: { title: "My first todo!" } }
        { create: { title: "My second todo!" } }
      ]
    }
  ) {
    todoList {
      title
      todos {
        title
      }
    }
  }
}
```

You can also update, delete, query all or individual entries for the models you defined above. Here's an example querying for the first 100 todoList items, and their linked todos:

```graphql
{
  todoListCollection(first: 100) {
    edges {
      node {
        title
        todos {
          title
        }
      }
    }
  }
}
```

You can learn more about the CLI [here](https://grafbase.com/cli). The CLI is [open source](https://github.com/grafbase/grafbase), and built with Rust.

We'd love to hear your feedback and ideas, so join us on [Discord](https://discord.gg/grafbase).


Changelog

Unique directive now available

Grafbase CLI now supports live reloading

Grafbase CLI now available