Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

unpartial

Package Overview
Dependencies
Maintainers
1
Versions
26
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

unpartial

Unpartial a partialed object

  • 1.0.5
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
27K
decreased by-6.06%
Maintainers
1
Weekly downloads
 
Created
Source

unpartial

NPM version NPM downloads

GitHub NodeJS Codecov

Visual Studio Code Wallaby.js

Unpartial a type.

It is very common to define a config type and Partial<> it in a function argument. When we received the argument, we want to merge it with our default config before using it:

import { unpartial } from 'unpartial'

interface Config {
  require: { a: number }
  optional?: { a: number }
}
const defaultConfig: Config = { require: { a: 1 } }

function foo(givenConfig?: Partial<Config>) {
  const config = unpartial(defaultConfig, givenConfig);
  // use config with type safety
}

Code completion is available as you type:

const config = unpartial(defaultConfig, { /* code completion here */});

It also supports merging two default configs. This is useful when you are extending the interface from another package/class.

import { unpartial } from 'unpartial'

import { Option, defaultOption } from 'another-package'

interface MyOption extends Option { ... }

const myDefaultOption = { ... }

function foo(givenOption?: Partial<MyOption>) {
  const option = unpartial(defaultOption, myDefaultOption, givenOption)
}

This is deprecated because currently TypeScript does not support optional generic type, so it is not possible to create a satisfactory signature that works with both implicit and explicit type.

Instead, please use composition when combining 3 or more values:

unpartial(unpartial(defaultOption, myDefaultOption), givenOption)

There are 3 more functions available in this library:

  • unpartialRecursively(): unpartial() deeply.
    In practice, this does not seem to be useful. Maybe will be deprecated and removed in the future.
  • required(): an alternative version of unpartial() with a different type management.
    This will become identical to unpartial() in the future.
  • requiredDeep(): an alternative version of unpartialRecursively() with a different type management.
    This will become identical to unpartial() in the future.

unpartial is also exposed through type-plus. It contains many more functions and type utilities.

Feel free to check it out.

Contribute

# after fork and clone
pnpm install

# begin making changes
git checkout -b <branch>
pnpm watch

# after making change(s)
git commit -m "<commit message>"
git push

# create PR

Wallaby.js

Wallaby.js

This repository contributors are welcome to use Wallaby.js OSS License to get test results immediately as you type, and see the results in your editor right next to your code.

FAQs

Package last updated on 03 Jun 2023

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc