13 replies

Array<string> vs Record<key, true>?

So, this is a call for mental help lol. First this is a taste question, is not a necesary question and is clearly a dum question, but i wanna ask any way.

In my lastest months i been working usually in backend stuff, and primary using Prisma for schema and some queries, because is VPS not serverless, Kysely for some complex queries, and Zod for validation (DTO and others stuffs). All is good, everything work perfectly (ignoring the lack of some query functionalities in Prisma). But there is something that really BOTHER me when i read the code. For example

when picking fields in a prisma query, you do a something like this:

const query = await prisma.user.findMany({
  select:{ id: true, name: true, last_name: true }
})

const query = await prisma.user.findMany({
  select:{ id: true, name: true, last_name: true }
})

This kind of API is truly intuitive, feels nice. But then using Kysely is something like this:

const query = await kysely.selectFrom('User').select(['id','name','last_name']).execute()

const query = await kysely.selectFrom('User').select(['id','name','last_name']).execute()

This also feels nice, but when the query grow too much, usually when conditionals are added or too much select fields added, i feel that the kysely way it feels more verbose.

Another case is validation library like zod, i really love zod, too much hahaha.

zodDataSchema.pick({
    name: true,
    hello: true,
});

zodDataSchema.pick({
    name: true,
    hello: true,
});

Again, they use the Record<key, true> approach to pick/omit/required/partial objects, just like prisma does.

But then most utility libraries like lodash, or remedajs use Array<string> approach, this make me create my own libraries to have similar approach to Record<key, true> approach

//Remeda js way
const remeda = R.pick(data, ["age", "isAdmin", "name"]);
//Example custom zod way
const custom = util.pick(data, {
    age: true,
    isAdmin: true,
    name: true,
});

//Remeda js way
const remeda = R.pick(data, ["age", "isAdmin", "name"]);
//Example custom zod way
const custom = util.pick(data, {
    age: true,
    isAdmin: true,
    name: true,
});

So, my question is, is healthy and good that i wanna choose only one way of doing picking/omit in objects? I been building my own alternatives to Remeda or Kysely but Record<key, true> approach, what do you think? Do you like it? I'm just testing.

TTC

Theo's Typesafe Cult•3y ago•

13 replies

oljimenez

Array<string> vs Record<key, true>?

const query = await prisma.user.findMany({
  select:{ id: true, name: true, last_name: true }
})

const query = await prisma.user.findMany({
  select:{ id: true, name: true, last_name: true }
})

This kind of API is truly intuitive, feels nice. But then using Kysely is something like this:

const query = await kysely.selectFrom('User').select(['id','name','last_name']).execute()

const query = await kysely.selectFrom('User').select(['id','name','last_name']).execute()

zodDataSchema.pick({
    name: true,
    hello: true,
});

zodDataSchema.pick({
    name: true,
    hello: true,
});

//Remeda js way
const remeda = R.pick(data, ["age", "isAdmin", "name"]);
//Example custom zod way
const custom = util.pick(data, {
    age: true,
    isAdmin: true,
    name: true,
});

//Remeda js way
const remeda = R.pick(data, ["age", "isAdmin", "name"]);
//Example custom zod way
const custom = util.pick(data, {
    age: true,
    isAdmin: true,
    name: true,
});

Array<string> vs Record<key, true>?

Array<string> vs Record<key, true>?

Similar Threads

Similar Threads

Similar Threads