Directus Adapters

[e8ward]

For those who want to use their Directus as a database and wanted to store Next-Auth user session, data, etc

Most of the time Directus SDK sucks. So i had a custom adapter using axios.

Word of Caution
it might not work, im just sharing it so that you can get an idea on where to start.

import axios from 'axios'

const d = axios.create({
  baseURL: 'PUT YOUR DIRECTUS URL HERE',
})

export function DirectusAdapter() {
  return {
    createUser: async (data) => {
      const { data: user } = await d.post('/items/user', data)
      return user.data
    },

    getUser: async (id) => {
      const { data } = await d.get(`items/user?filter[id][_eq]=${id}`)
      return data.data[0]
    },

    getUserByEmail: async (email) => {
      const { data } = await d.get(
        `/items/user?filter[email][_eq]=${email}`
      )
      return data.data[0]
    },

    getUserByAccount: async ({ providerAccountId, provider }) => {
      const { data } = await d.get(
        `items/account?filter[providerAccountId][_eq]=${providerAccountId}&filter[provider][_eq]=${provider}&fields[]=*.*`
      )
      const { data: account } = data
      if (!account || !account[0]) return
      return account[0].userId
    },

    updateUser: async ({ id, ...data }) => {
      await d.patch(`items/user/${id}`, data)
    },

    linkAccount: async (data) => {
      const { data: account } = await d.post('items/account', data)
      return account
    },

    getSessionAndUser: async (sessionToken) => {
      const session_data = await d.get(
        `items/session?filter[sessionToken][_eq]=${sessionToken}`
      )
      let session = session_data.data.data[0]
      session.expires = new Date(session.expires)
      session = {
        id: session.id,
        expires: session.expires,
        sessionToken: session.sessionToken,
        userId: session.userId,
      }

      if (!session) return

      const user_data = await d.get(`items/user/${session.userId}`)
      const user = user_data.data.data

      if (!user) return

      return { session, user }
    },

    createSession: async (session) => {
      await d.post('/items/session', session)
      return session
    },

    updateSession: async ({ sessionToken }) => {
      const { data } = await d.get(
        `items/session?filter[sessionToken][_eq]=${sessionToken}`
      )
      const id = data.data[0].id
      await d.patch(`items/session/${id}`, data)
    },

    deleteSession: async (sessionToken) => {
      const { data } = await d.get(
        `items/session?filter[sessionToken][_eq]=${sessionToken}`
      )
      const id = data.data[0].id
      await d.delete(`items/session/${id}`)
    },

    // Delete user info (Future)
    // deleteUser: async (id) => await d.delete(`items/auth_user/${id}`),

    // Unlink Account info (Future)
    // unlinkAccount: async ({ providerAccountId, provider }) => {
    //   console.log('running unlinkAccount', { providerAccountId, provider })
    //   const { data } = await d.get(
    //     `items/account?filter[providerAccountId][_eq]=${providerAccountId}&filter[provider][_eq]=${provider}`
    //   )
    //   const id = data.data[0].id
    //   await d.delete(`items/account/${id}`)
    //   return
    // },
  }
}

Hope this help you guys who uses Directus

[belov38]

Thanks for the Directus Adapter,
Just wondering why Directus SDK sucks? Have you tried to use new Directus SDK?

[triplecasquette]

Hey @belov38 can you told me how you connect to directus and next-auth?

[belov38]

Finally I deciden do not use any Directus Adapters. Directus is a UI for you Database. So you can use well implemented DB adapters like prisma and point Directus to the same DB.

To make your DB environment a bit clear you can create all next-auth tables in the separate schema (i use postgress)
To set up directus search in different schemas use environment var
DB_SEARCH_PATH: 'array:string:public,auth'

// schema.prisma
datasource db {
  provider = "postgresql"
  url      = "postgresql://your_username:your_password@localhost:5432/directus10?schema=auth"
}

In this example all next-auth tables reside in the auth schema and you can see all tables in Directus.

BTW, using Directus via Adapter adds extra point of failure.

[Nisthar]

@belov38 don't you need to create a duplicate user table for just doing auth?