Nested Reference Model

[conduongtong]

I follow this instruction: https://elysiajs.com/patterns/reference-models.html
With this code:

// auth.model.ts
import { Elysia, t } from 'elysia'

export const authModel = new Elysia()
    .model({
        sign: t.Object({
            username: t.String(),
            password: t.String()
        })
    })

// index.ts
import { Elysia } from 'elysia'
import { authModel } from './auth.model.ts'

const app = new Elysia()
    .use(authModel)
    .post('/sign-in', ({ body }) => body, {
            // with auto-completion for existing model name
        body: 'sign',
        response: 'sign'
    })

How can I use it inside t.Object() like below:

const app = new Elysia()
    .use(authModel)
    .post('/sign-in', ({ body }) => body, {
            // with auto-completion for existing model name
        body: t.Object({ sign: 'sign' }),
        response: 'sign'
    })

The reason is I have a 'pagination' model which look like this:

body: t.Object({
  results: modelName,
  page: t.Number(),
  ...
})

With reference model I have to create each pagination for models, how can I achieve it?

[SaltyAom]

You can use model remapping to get the reference from defined models.

So you should be able to do something like this:

const a = new Elysia()
	.model({
		sign: t.Object({
			username: t.String(),
			password: t.String()
		})
	})
	.model(({ sign }) => ({
		signWithPagination: t.Object({
			results: sign,
			page: t.Number()
		})
	}))

Then you can just use the reference model in there:

const app = new Elysia()
	.use(a)
	.post('/sign-in', ({ body }) => body, {
		body: 'signWithPagination'
	})
	.listen(3000)

[conduongtong]

@SaltyAom So basically I still have to create double models because every model have pagination, for example: user, userWithPagination, role, roleWithPagination,...
That's not what I'm looking for

[Nmans01]

@SaltyAom I see that sign from your example, once mapped into signWithPagination, is no longer typed as a t Schema, but is instead of type t.Unsafe. Is there a specific reason for this?

I would like to be able to spread the properties of a predefined model like sign into another model, like signWithPagination in your example, or be able to use t.Composite to combine the two schemas at their root level. I feel like this may appease OP's issue as well.