Skip to content

Implement DeepStrictPick as logic, not type #3

@kakasoo

Description

@kakasoo

Feature Request

  • Extensions of existing features
  • Propose a type that didn't exist before

Type Expectation

This is not a type, but it means a function that makes it have the same return type as the name of the type. The name of the function cannot be used because it is already the same as the name of the type. Therefore, a naming convention is also required.

Example Type

// Example Input Type
type Input = {
  user: {
    name: string;
    age: number;
  };
};

// Current inferred type or behavior:
// "user" | "user.name" | ...

// Expected behavior or type:
// "user.age" should be inferred or handled differently.

const picked = DeepStrictPick({} as Example, 'user.age'); // for example, { user: { age: 1 } }

Proposed Solution

I've already implemented 'deepStrictAssert', but I want to change this function to 'deepStrictPick', and I want to change that to 'deepStrictPick'. I want to separate the neming convention by starting with a capital letter and logic with lowercase letters.

Use Case

Additional Context

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions