FEATURE REQUEST: More options for HideField

[FinaritrAndrianiaina]

---

name: FEATURE REQUEST: More options for HideField
about: "Add more options to Hide Field"

---

PS: I don't know if there are already a way to do this.

What problem this will Solve

Example: we can use @HideField like this

model Post {
  id        String   @id @default(cuid())
  title     String
  // @HideField({output:false,input:true})
  createdAt DateTime @default(now())
  /// @HideField({output:false,input:true})
  updatedAt DateTime @updatedAt
  body      String
}

But what if we can specify in which Input we want to add the @HideField decorator and have something like that:

model Post {
  id        String   @id @default(cuid())
  title     String
  /// @HideField({output:false,createInput:true,whereInput:false})
  createdAt DateTime @default(now())
  /// @HideField({output:false,createInput:true,whereInput:false})
  updatedAt DateTime @updatedAt
  body      String
}

Results:

\\post-create.input.ts
@InputType()
export class PostCreateInput {
    @Field(() => String, {nullable:true})
    id?: string;

    @Field(() => String, {nullable:false})
    title!: string;

    @HideField()
    createdAt?: Date | string;

    @HideField()
    updatedAt?: Date | string;

    @Field(() => String, {nullable:false})
    body!: string;
}

\\post-where.input.ts
@InputType()
export class PostWhereInput {
    @Field(() => [PostWhereInput], {nullable:true})
    AND?: Array<PostWhereInput>;

    @Field(() => [PostWhereInput], {nullable:true})
    OR?: Array<PostWhereInput>;

    @Field(() => [PostWhereInput], {nullable:true})
    NOT?: Array<PostWhereInput>;

    @Field(() => StringFilter, {nullable:true})
    id?: StringFilter;

    @Field(() => StringFilter, {nullable:true})
    title?: StringFilter;


    // @HideField()
    @Field(() => StringFilter, {nullable:true})
    createdAt?: DateTimeFilter;

    // @HideField()
    @Field(() => StringFilter, {nullable:true})
    updatedAt?: DateTimeFilter;

    @Field(() => StringFilter, {nullable:true})
    body?: StringFilter;
}

[unlight]

Is whereInput means all names like UserWhereInput, UserWhereUniqueInput, UserScalarWhereWithAggregatesInput, etc. ?

[FinaritrAndrianiaina]

Yes, it is. But what if the input in HideField just apply on CreateInput and UpdateInput not on WhereInput. Because we don't need to have autogenerated field on CreateInput or UpdtateInput but need it for querying in WhereInput. But for the WhereUniqueInput I think it's not necessary to control it

[unlight]

🎉 This issue has been resolved in version 12.1.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[unlight]

@FinaritrAndrianiaina
Please, check https://github.com/unlight/prisma-nestjs-graphql#hidefield updated @HideField() documentation