V3: custom methods usage

[krislintigo]

While setup Feathers Pinia v3 I'm losing custom methods. Setup below:

export default defineNuxtPlugin((nuxt) => {
  const storageKey = 'feathers-jwt'
  const host =
    (import.meta.env.VITE_MYAPP_API_URL as string) || 'http://localhost:3030'
  const connection = socketio<ServiceTypes>(
    io(host, { transports: ['websocket'] })
  )

  const feathersClient = createClient(connection, {
    storageKey,
  })
  console.log('CREATE CLIENT', feathersClient.service('users'))
  const api = createPiniaClient(feathersClient, {
    pinia: nuxt.$pinia,
    // ssr: process.server,
    ssr: false,
    idField: '_id',
    whitelist: [],
    paramsForServer: [],
    skipGetIfExists: true,
    customSiftOperators: {},
  })
  console.log('CREATE PINIA CLIENT', api.service('users'))

  return { provide: { api } }
})

In this setup, all methods available in feathers client, but only default methods in pinia client api:

[marshallswain]

Oh good catch. I need to proxy those methods in the wrapping service.

[marshallswain]

Hmm. The JS part is easy to support, but TS is another story. As a workaround, you can access custom methods at api.service('my-service').service.isUserExists, for example.

[marshallswain]

We've had some internal discussion on how to fix the headache with custom method types. We'll likely be changing how custom methods are called in Feathers v6. The syntax will be something like service('my-service').call('custom-method-name', data)

I'm going to postpone working on this issue until that time, because the TS work is prohibitive, at least for me.