Socket
Socket
Sign inDemoInstall

failables

Package Overview
Dependencies
0
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

failables


Version published
Maintainers
1
Created

Readme

Source

failables

Failables are a clean, consistent, async-friendly, network-friendly result type.

Successful results are represented as failables of type SUCCESS, with the result stored in the payload.

Empty results are neither success nor failure; they are represented as failables of type EMPTY, and of course have no payload. Calling success without a payload will result in an empty failable (not a success).

Instead of representing errors sometimes by a result code, sometimes by a magic number, and sometimes by throwing an exception, consistently represent errors as failables of type FAILURE, with the error message stored in the payload.

That's all there is to it.

usage

  const result1 = success('foo') // first parameter is payload
  const result2 = success('foo', { timesCalled: 7 })  // second (optional) parameter is metadata
  const result3 = failure('trouble!') // payload is error message
  const result4 = failure('trouble!', { userId: 'fred' })  // all failables can include metadata
  const result5 = empty() // empty failables have no payload
  const result6 = empty({ userId: 'fred' })  // for empty, the first (optional) parameter is metadata
  
  const answer = payload(result1) // extract the payload
  const metadata = meta(result2) // extract the metadata
  if (isFailure(result4)) return result4 // a common pattern: if a failure is encountered in a
                                         // failable-returning function, just return the failure directly

documentation

creation

  success(payload, meta) // returns a success failable
  failure(payload, meta) // returns a failure failable
  empty(meta)            // returns an empty failable

tests

  isFailable(object)  // whether the object represents a failable
  isSuccess(failable) // whether the failable is success
  isFailure(failable) // whether the failable is failure
  isEmpty(failable)   // whether the failable is empty

elements

  payload(failable) // extracts the failable's payload
  meta(failable)    // extracts the failable's metadata

list operations

  anyFailed(list)    // whether any in the list failed
  firstFailure(list) // the first failure in the list

assertions

  assertSuccess(failable, payload) // assert that the failable is success
  assertFailure(failable, payload) // assert that the failable is failure
  assertEmpty(failable)            // assert that the failable is empty

utility

  hydrate(failable) // returns an object with kind, payload, and meta fields

Keywords

FAQs

Last updated on 03 Nov 2017

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

Packages

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc