JavascriptMick Comments - Answer Overflow

JavascriptMick

Explore posts from servers

•Created by JavascriptMick on 12/16/2024 in #❓・help

multi-version rest api

@kapa.ai none of your solutions work. I have updated the discussion here (https://github.com/nitrojs/nitro/discussions/2413#discussioncomment-11601171) in the hope of getting a response from the Nitro team

20 replies

NNuxt

•Created by JavascriptMick on 12/16/2024 in #❓・help

multi-version rest api

@kapa.ai ok so this nearly works, let me explain. This route rules configuration proxys all v2 routes to the base versions...

  routeRules: {
    '/api/v2/**': { proxy: '/api/**' }
  },

  routeRules: {
    '/api/v2/**': { proxy: '/api/**' }
  },

But what if I have a route that is implemented differently for V2? (e.g. /api/v2/stoopid) the above configuration ensures that the V2 version of the handler is ignored. Is it possible to have a catch all like above but somehow exclude specific routes from the catch all, something like this...

  routeRules: {
    '/api/v2/stoopid': { proxy: 'false' },
    '/api/v2/**': { proxy: '/api/**' }
  },

  routeRules: {
    '/api/v2/stoopid': { proxy: 'false' },
    '/api/v2/**': { proxy: '/api/**' }
  },

Alternatively, I will need to individually specify proxies for all default routes that have no v2 version. this is simple but tedious.

  
routeRules: {
    '/api/v2/someroute': { proxy: '/api/someroute' },
    '/api/v2/someotherroute': { proxy: '/api/someotherroute' },
    ... etc for all routes that have no v2 version
  },

  
routeRules: {
    '/api/v2/someroute': { proxy: '/api/someroute' },
    '/api/v2/someotherroute': { proxy: '/api/someotherroute' },
    ... etc for all routes that have no v2 version
  },

Here is a discussion that I think is relevant although it is not resolved very clearly (https://github.com/nitrojs/nitro/discussions/2413) so, I guess my question is, is it possible to include a 'catch all' glob based route in nuxtConfig but also have exclusions to the catch all for specific routes that have V2 version?

20 replies

NNuxt

•Created by JavascriptMick on 12/16/2024 in #❓・help

multi-version rest api

@kapa.ai this doesn't work, it doesn't compile. can I do it with route rules in nuxt.config?

20 replies

PPrisma

•Created by JavascriptMick on 11/14/2024 in #help-and-questions

gin index

FTR, this worked

@@index([my_string_column(ops: raw("gin_trgm_ops"))], type: Gin)

@@index([my_string_column(ops: raw("gin_trgm_ops"))], type: Gin)

4 replies

PPrisma

•Created by JavascriptMick on 4/21/2024 in #help-and-questions

children and favourite child (ambiguous relation)

ok, never mind I figured it out. I want to apologise to anybody who is triggered by this example. I know these type of relationships can be fraught and vexxed. I only seek to understand.

model Parent {
  id                 Int         @id @default(autoincrement())
  
  favourite_child_id Int
  favourite_child    Child       @relation("ParentHasFavourite", fields: [favourite_child_id], references: [id])

  children           Child[]     @relation("ParentHasChildren")

  @@map("parent")
}

model Child {
  id              Int         @id @default(autoincrement())

  parent_id       Int
  parent          Parent   @relation("ParentHasChildren", fields: [parent_id], references: [id])

  parents_who_love_me_most Parent[] @relation("ParentHasFavourite")

  @@map("child")
}

model Parent {
  id                 Int         @id @default(autoincrement())
  
  favourite_child_id Int
  favourite_child    Child       @relation("ParentHasFavourite", fields: [favourite_child_id], references: [id])

  children           Child[]     @relation("ParentHasChildren")

  @@map("parent")
}

model Child {
  id              Int         @id @default(autoincrement())

  parent_id       Int
  parent          Parent   @relation("ParentHasChildren", fields: [parent_id], references: [id])

  parents_who_love_me_most Parent[] @relation("ParentHasFavourite")

  @@map("child")
}

2 replies

NNuxt

•Created by JavascriptMick on 2/17/2024 in #❓・help

Can I put multiple Favicon assets in public?

for now, I have dumped them all in and done this in my nuxt.config.ts...

  app: {
    head: {
      htmlAttrs: {
        lang: 'en'
      },
      title: 'Blah',
      link: [
        { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' },
        {
          rel: 'icon',
          type: 'image/png',
          sizes: '32x32',
          href: '/favicon-32x32.png'
        },
        {
          rel: 'icon',
          type: 'image/png',
          sizes: '16x16',
          href: '/favicon-16x16.png'
        },
        {
          rel: 'apple-touch-icon',
          sizes: '180x180',
          href: '/apple-touch-icon.png'
        },
        { rel: 'manifest', href: '/site.webmanifest' }
      ]
    }
  },

  app: {
    head: {
      htmlAttrs: {
        lang: 'en'
      },
      title: 'Blah',
      link: [
        { rel: 'icon', type: 'image/x-icon', href: '/favicon.ico' },
        {
          rel: 'icon',
          type: 'image/png',
          sizes: '32x32',
          href: '/favicon-32x32.png'
        },
        {
          rel: 'icon',
          type: 'image/png',
          sizes: '16x16',
          href: '/favicon-16x16.png'
        },
        {
          rel: 'apple-touch-icon',
          sizes: '180x180',
          href: '/apple-touch-icon.png'
        },
        { rel: 'manifest', href: '/site.webmanifest' }
      ]
    }
  },

I guess I'll see how it goes

2 replies

TtRPC

•Created by JavascriptMick on 6/2/2023 in #❓-help

Use onError to change an application error into a TRPCError?

See example in my boilerplate repo here https://github.com/JavascriptMick/nuxt3-boilerplate/blob/master/server/trpc/trpc.ts

8 replies

TtRPC

•Created by JavascriptMick on 6/2/2023 in #❓-help

Use onError to change an application error into a TRPCError?

ah nice, thanks guys, yep this works.....

const t = initTRPC.context<Context>().create({
  errorFormatter: (opts)=> {
    const { shape, error } = opts;
    if (!(error.cause instanceof AccountLimitError)) {
      return shape;
    }
    return {
      ...shape,
      data: {
        ...shape.data,
        httpStatus: 401,
        code: 'UNAUTHORIZED'
      },
    };
  }
})

const t = initTRPC.context<Context>().create({
  errorFormatter: (opts)=> {
    const { shape, error } = opts;
    if (!(error.cause instanceof AccountLimitError)) {
      return shape;
    }
    return {
      ...shape,
      data: {
        ...shape.data,
        httpStatus: 401,
        code: 'UNAUTHORIZED'
      },
    };
  }
})

8 replies

NNuxt