Coder Social home page Coder Social logo

level-ws's Introduction

level-ws

A basic writable stream for abstract-level databases, using Node.js core streams. This is not a high-performance stream. If benchmarking shows that your particular usage does not fit then try one of the alternative writable streams that are optimized for different use cases.

📌 To instead write data using Web Streams, see level-web-stream.

level badge npm Node version Test Coverage Standard Common Changelog Donate

Usage

If you are upgrading: please see UPGRADING.md.

const { Level } = require('level')
const WriteStream = require('level-ws')

const db = new Level('./db', { valueEncoding: 'json' })
const ws = new WriteStream(db)

ws.on('close', function () {
  console.log('Done!')
})

ws.write({ key: 'alice', value: 42 })
ws.write({ key: 'bob', value: 7 })

// To delete entries, specify an explicit type
ws.write({ type: 'del', key: 'tomas' })
ws.write({ type: 'put', key: 'sara', value: 16 })

ws.end()

API

ws = new WriteStream(db[, options])

Create a writable stream that operates in object mode, accepting batch operations to be committed with db.batch() on each tick of the Node.js event loop. The optional options argument may contain:

  • type (string, default: 'put'): default batch operation type if not set on indididual operations.
  • maxBufferLength (number, default Infinity): limit the size of batches. When exceeded, the stream will stop processing writes until the current batch has been committed.
  • highWaterMark (number, default 16): buffer level when stream.write() starts returning false.

Contributing

Level/level-ws is an OPEN Open Source Project. This means that:

Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.

See the Contribution Guide for more details.

License

MIT

level-ws's People

Contributors

dependabot[bot] avatar greenkeeper[bot] avatar greenkeeperio-bot avatar juliangruber avatar mcollina avatar n370 avatar ralphtheninja avatar rvagg avatar vweevers avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

level-ws's Issues

An in-range update of level is breaking the build 🚨

Version 3.0.1 of level was just published.

Branch Build failing 🚨
Dependency level
Current Version 3.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

level is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 9 commits.

  • cec4d9a 3.0.1
  • 4d4f881 update changelog (#102)
  • 19c6fde Merge pull request #101 from Level/postinstall
  • 3ee116a ignore postinstall failures
  • 5d07a5e add node 10
  • b961967 Merge pull request #95 from rasmuserik/master
  • 1047266 fix typo in README.md
  • e42c0b0 Merge pull request #93 from Level/greenkeeper/standard-11.0.0
  • 7c54885 chore(package): update standard to version 11.0.0

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of level is breaking the build 🚨

Version 2.0.0 of level was just published.

Branch Build failing 🚨
Dependency level
Current Version 1.7.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

level is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 26 commits.

  • efb9990 2.0.0
  • 64f5f47 Merge pull request #65 from ralphtheninja/master
  • bf0de16 options are passed to encoding-down (level-codec indirectly)
  • 27965de Merge pull request #63 from ralphtheninja/master
  • 9a8aef8 :arrow_up: bump level-packager
  • 1e1ef18 tweak readme (#62)
  • e4b04be Merge pull request #60 from Level/standard
  • 06902e3 standard: fix newlines at end of files
  • 6a4145d add standard
  • 100b134 Merge pull request #56 from Level/greenkeeper/leveldown-2.0.0
  • 5ff4e3d fix(package): update leveldown to version 2.0.0
  • 8a63d6b Merge pull request #55 from Level/greenkeeper/leveldown-1.9.0
  • 47a54c3 fix(package): update leveldown to version 1.9.0
  • 5438517 2.0.0-rc3
  • 19ceefa :arrow_up: bump level-packager to rc3

There are 26 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of readable-stream is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.3.5 of readable-stream was just published.

Branch Build failing 🚨
Dependency readable-stream
Current Version 2.3.4
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

readable-stream is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v2.3.5
Commits

The new version differs by 4 commits ahead by 4, behind by 1.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Release v1.0.0

Don't forget to

Should add the removal of destroySoon but that's also missing from the changelog, can wait. We can do another pass on the upgrade guide and changelog before release.

An in-range update of readable-stream is breaking the build 🚨

Version 2.3.4 of readable-stream was just published.

Branch Build failing 🚨
Dependency readable-stream
Current Version 2.3.3
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

readable-stream is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 11 commits.

  • a8c2df1 Bumped v2.3.4
  • f94381c Fix browser support for util.inspect.custom fix
  • fd1efbf removed saucelabs testing for now
  • fc6db13 Proper fix, soft-detecting there is a custom inspect.
  • 6ec7d8a Revert "Fix tests for Node master / citgm"
  • 7dc90fe Fix tests for Node master / citgm
  • 41a3301 Updated dependencies
  • 56d3087 Updated README
  • b4a83e0 Working on old nodes
  • fa8729c built 8.9.4.
  • 56d9356 add lrlna to readme

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Remove patching db

Current API patches db by adding a .createWriteStream(). I propose we change this so this module only exports a WriteStream(db, options) constructor.

Simplify verification logic in tests

Instead of doing multiple gets, take e.g. a db.iterator() + level-concat-iterator and compare arrays. This way we can have more massive arrays of data and less spammy tests.

Change maxBufferLength logic

level-ws/level-ws.js

Lines 32 to 35 in 1823145

if (self._options.maxBufferLength &&
self._buffer.length > self._options.maxBufferLength) {
self.once('_flush', next)
} else {

Rather than ignoring writes, we can pause until the current buffer is flushed. Along the lines of:

self.once('_flush', function (err) {
  if (err) return next(err)
  self._write(d, enc, next)
}) 

Release 2.0.0

Major due to readable-stream bump and dropping node 9.

An in-range update of tape is breaking the build 🚨

Version 4.9.1 of tape was just published.

Branch Build failing 🚨
Dependency tape
Current Version 4.9.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

tape is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 10 commits.

  • 050b318 v4.9.1
  • 73232c0 [Dev Deps] update js-yaml
  • 8a2d29b [Deps] update has, for-each, resolve, object-inspect
  • c6f5313 [Tests] add eclint and eslint, to enforce a consistent style
  • 45788a5 [Dev Deps] update concat-stream
  • ec4a71d [fix] Fix bug in functionName regex during stack parsing
  • 7261ccc Merge pull request #433 from mcnuttandrew/add-trb
  • 6cbc53e Add tap-react-browser
  • 9d501ff [Dev Deps] use ~ for dev deps; update to latest nonbreaking
  • 24e0a8d Fix spelling of "parameterize"

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

can we somehow remove/replace level or change circular problems? (iojs)

Ok, so correct me if I'm wrong.

level depends on level-packager which depends on levelup which devDepends on level-ws (remove-write-stream branch) which in turn devDepends on level.

So I have this scenario:

  • clone level-ws and checkout tweaks branch
  • npm install fails on iojs since [email protected] is used and that version does not work with iojs

Which obviously leads us to the situation where we should fix level so it works with iojs (in order to get level-ws to install properly).

This basically means updating level to use leveldown@~1.0.0 and also update level-packager to use an updated levelup which devDepends on this module that we are trying to install.

It seems a bit circular to me. Am I missing something here?

/cc @rvagg

Link to a specific version of node.js docs

That matches our readable-stream version.

Creates a [Writable](http://nodejs.org/docs/latest/api/stream.html#stream_class_stream_writable_1) stream which operates in **objectMode**, accepting objects with `'key'` and `'value'` pairs on its `write()` method.

publish v0.1.0

I commited the package.json, as I thought I was npm owner :(. I'm not so.. :)

Remove toString()?

And if not, maybe we should change the name from 'LevelUP.WriteStream' to something else? Needs test as well.

An in-range update of level is breaking the build 🚨

Version 4.0.0 of level was just published.

Branch Build failing 🚨
Dependency level
Current Version 3.0.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

level is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v4.0.0

Changed

Removed

Commits

The new version differs by 7 commits ahead by 7, behind by 3.

  • 2e95a49 4.0.0
  • 8181132 Prepare 4.0.0 (#108)
  • 79d209b bump level-packager to ^3.0.0
  • 44789fb update changelog
  • a7502af updating to non-broken opencollective-postinstall, instead of opencollective (#106)
  • ddd4a78 fix(package): update leveldown to version 4.0.0 (#105)
  • 1baa979 remove node 4 :fire:

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Race conditions

discovered two race conditions running the tests on node 3:

TAP version 13
# test simple WriteStream
ok 1 no error
ok 2 no error
ok 3 not writable
ok 4 not readable
ok 5 no error
ok 6 WriteStream data #0 has correct value
ok 7 no error
ok 8 WriteStream data #1 has correct value
ok 9 no error
ok 10 WriteStream data #2 has correct value
ok 11 no error
ok 12 WriteStream data #3 has correct value
ok 13 no error
ok 14 WriteStream data #4 has correct value
ok 15 no error
ok 16 WriteStream data #5 has correct value
ok 17 no error
ok 18 WriteStream data #6 has correct value
ok 19 no error
ok 20 WriteStream data #7 has correct value
ok 21 no error
ok 22 WriteStream data #8 has correct value
ok 23 no error
ok 24 WriteStream data #9 has correct value
# test WriteStream with async writes
ok 25 no error
ok 26 no error
ok 27 not writable
ok 28 not readable
ok 29 no error
ok 30 WriteStream data #0 has correct value
ok 31 no error
ok 32 WriteStream data #1 has correct value
ok 33 no error
ok 34 WriteStream data #2 has correct value
ok 35 no error
ok 36 WriteStream data #3 has correct value
ok 37 no error
ok 38 WriteStream data #4 has correct value
ok 39 no error
ok 40 WriteStream data #5 has correct value
ok 41 no error
ok 42 WriteStream data #6 has correct value
ok 43 no error
ok 44 WriteStream data #7 has correct value
ok 45 no error
ok 46 WriteStream data #8 has correct value
ok 47 no error
ok 48 WriteStream data #9 has correct value
# test end accepts data
ok 49 no error
ok 50 no error
ok 51 not writable
ok 52 not readable
ok 53 no error
ok 54 WriteStream data #0 has correct value
ok 55 no error
ok 56 WriteStream data #1 has correct value
ok 57 no error
ok 58 WriteStream data #2 has correct value
ok 59 no error
ok 60 WriteStream data #3 has correct value
ok 61 no error
ok 62 WriteStream data #4 has correct value
ok 63 no error
ok 64 WriteStream data #5 has correct value
ok 65 no error
ok 66 WriteStream data #6 has correct value
ok 67 no error
ok 68 WriteStream data #7 has correct value
ok 69 no error
ok 70 WriteStream data #8 has correct value
ok 71 no error
ok 72 WriteStream data #9 has correct value
# test destroySoon()
ok 73 no error
ok 74 no error
ok 75 not writable
ok 76 not readable
ok 77 no error
ok 78 WriteStream data #0 has correct value
ok 79 no error
ok 80 WriteStream data #1 has correct value
ok 81 no error
ok 82 WriteStream data #2 has correct value
ok 83 no error
ok 84 WriteStream data #3 has correct value
ok 85 no error
ok 86 WriteStream data #4 has correct value
ok 87 no error
ok 88 WriteStream data #5 has correct value
ok 89 no error
ok 90 WriteStream data #6 has correct value
ok 91 no error
ok 92 WriteStream data #7 has correct value
ok 93 no error
ok 94 WriteStream data #8 has correct value
ok 95 no error
ok 96 WriteStream data #9 has correct value
# test destroy()
ok 97 no error
ok 98 no error
ok 99 is writable
ok 100 not readable
ok 101 is writable
ok 102 not readable
ok 103 is writable
ok 104 not readable
ok 105 is writable
ok 106 not readable
ok 107 is writable
ok 108 not readable
ok 109 is writable
ok 110 not readable
ok 111 is writable
ok 112 not readable
ok 113 is writable
ok 114 not readable
ok 115 is writable
ok 116 not readable
ok 117 is writable
ok 118 not readable
ok 119 is writable
ok 120 not readable
ok 121 is writable
ok 122 not readable
ok 123 not writable
ok 124 got expected error
ok 125 did not get value
ok 126 got expected error
ok 127 did not get value
ok 128 got expected error
ok 129 did not get value
ok 130 got expected error
ok 131 did not get value
ok 132 got expected error
ok 133 did not get value
ok 134 got expected error
ok 135 did not get value
ok 136 got expected error
ok 137 did not get value
ok 138 got expected error
ok 139 did not get value
ok 140 got expected error
ok 141 did not get value
ok 142 got expected error
ok 143 did not get value
# test json encoding
ok 144 no error
ok 145 no error
ok 146 not writable
ok 147 not readable
not ok 148 no error
  ---
    operator: notOk
    expected: false
    actual:   {}
    at: dispatchError (/home/travis/build/Level/level-ws/node_modules/level/node_modules/level-packager/node_modules/levelup/lib/util.js:64:35)
  ...
not ok 149 WriteStream data #aa has correct value
  ---
    operator: equal
    expected: NaN
    actual:   NaN
    at: dispatchError (/home/travis/build/Level/level-ws/node_modules/level/node_modules/level-packager/node_modules/levelup/lib/util.js:64:35)
  ...
ok 150 no error
ok 151 WriteStream data #ab has correct value
ok 152 no error
ok 153 WriteStream data #ac has correct value
ok 154 no error
ok 155 WriteStream data #ba has correct value
ok 156 no error
ok 157 WriteStream data #bb has correct value
ok 158 no error
ok 159 WriteStream data #bc has correct value
ok 160 no error
ok 161 WriteStream data #ca has correct value
ok 162 no error
ok 163 WriteStream data #cb has correct value
ok 164 no error
ok 165 WriteStream data #cc has correct value
# test del capabilities for each key/value
ok 166 no error
ok 167 no error
ok 168 got expected error
ok 169 did not get value
ok 170 got expected error
ok 171 did not get value
ok 172 got expected error
ok 173 did not get value
ok 174 got expected error
ok 175 did not get value
ok 176 got expected error
ok 177 did not get value
ok 178 got expected error
ok 179 did not get value
ok 180 got expected error
ok 181 did not get value
ok 182 got expected error
ok 183 did not get value
ok 184 got expected error
ok 185 did not get value
# test del capabilities as constructor option
ok 186 no error
ok 187 no error
ok 188 got expected error
ok 189 did not get value
ok 190 got expected error
ok 191 did not get value
ok 192 got expected error
ok 193 did not get value
ok 194 got expected error
ok 195 did not get value
ok 196 got expected error
ok 197 did not get value
ok 198 got expected error
ok 199 did not get value
ok 200 got expected error
ok 201 did not get value
ok 202 got expected error
ok 203 did not get value
ok 204 got expected error
ok 205 did not get value
# test type at key/value level must take precedence on the constructor
ok 206 no error
ok 207 no error
ok 208 got value
ok 209 got expected error
ok 210 did not get value
ok 211 got expected error
ok 212 did not get value
ok 213 got expected error
ok 214 did not get value
ok 215 got expected error
ok 216 did not get value
ok 217 got expected error
ok 218 did not get value
ok 219 got expected error
ok 220 did not get value
ok 221 got expected error
ok 222 did not get value
ok 223 got expected error
ok 224 did not get value
# test ignoring pairs with the wrong type
ok 225 no error
ok 226 no error
ok 227 got expected error
ok 228 did not get value
ok 229 got expected error
ok 230 did not get value
ok 231 got expected error
ok 232 did not get value
ok 233 got expected error
ok 234 did not get value
ok 235 got expected error
ok 236 did not get value
ok 237 got expected error
ok 238 did not get value
ok 239 got expected error
ok 240 did not get value
ok 241 got expected error
ok 242 did not get value
ok 243 got expected error
ok 244 did not get value
ok 245 got expected error
ok 246 did not get value

1..246
# tests 246
# pass  244
# fail  2
TAP version 13
# test simple WriteStream
ok 1 no error
ok 2 no error
ok 3 not writable
ok 4 not readable
ok 5 no error
ok 6 WriteStream data #0 has correct value
ok 7 no error
ok 8 WriteStream data #1 has correct value
ok 9 no error
ok 10 WriteStream data #2 has correct value
ok 11 no error
ok 12 WriteStream data #3 has correct value
ok 13 no error
ok 14 WriteStream data #4 has correct value
ok 15 no error
ok 16 WriteStream data #5 has correct value
ok 17 no error
ok 18 WriteStream data #6 has correct value
ok 19 no error
ok 20 WriteStream data #7 has correct value
ok 21 no error
ok 22 WriteStream data #8 has correct value
ok 23 no error
ok 24 WriteStream data #9 has correct value
# test WriteStream with async writes
ok 25 no error
ok 26 no error
ok 27 not writable
ok 28 not readable
ok 29 no error
ok 30 WriteStream data #0 has correct value
ok 31 no error
ok 32 WriteStream data #1 has correct value
ok 33 no error
ok 34 WriteStream data #2 has correct value
ok 35 no error
ok 36 WriteStream data #3 has correct value
ok 37 no error
ok 38 WriteStream data #4 has correct value
ok 39 no error
ok 40 WriteStream data #5 has correct value
ok 41 no error
ok 42 WriteStream data #6 has correct value
ok 43 no error
ok 44 WriteStream data #7 has correct value
ok 45 no error
ok 46 WriteStream data #8 has correct value
ok 47 no error
ok 48 WriteStream data #9 has correct value
# test end accepts data
ok 49 no error
ok 50 no error
ok 51 not writable
ok 52 not readable
ok 53 no error
ok 54 WriteStream data #0 has correct value
ok 55 no error
ok 56 WriteStream data #1 has correct value
ok 57 no error
ok 58 WriteStream data #2 has correct value
ok 59 no error
ok 60 WriteStream data #3 has correct value
ok 61 no error
ok 62 WriteStream data #4 has correct value
ok 63 no error
ok 64 WriteStream data #5 has correct value
ok 65 no error
ok 66 WriteStream data #6 has correct value
ok 67 no error
ok 68 WriteStream data #7 has correct value
ok 69 no error
ok 70 WriteStream data #8 has correct value
ok 71 no error
ok 72 WriteStream data #9 has correct value
# test destroySoon()
ok 73 no error
ok 74 no error
ok 75 not writable
ok 76 not readable
ok 77 no error
ok 78 WriteStream data #0 has correct value
ok 79 no error
ok 80 WriteStream data #1 has correct value
ok 81 no error
ok 82 WriteStream data #2 has correct value
ok 83 no error
ok 84 WriteStream data #3 has correct value
ok 85 no error
ok 86 WriteStream data #4 has correct value
ok 87 no error
ok 88 WriteStream data #5 has correct value
ok 89 no error
ok 90 WriteStream data #6 has correct value
ok 91 no error
ok 92 WriteStream data #7 has correct value
ok 93 no error
ok 94 WriteStream data #8 has correct value
ok 95 no error
ok 96 WriteStream data #9 has correct value
# test destroy()
ok 97 no error
ok 98 no error
ok 99 is writable
ok 100 not readable
ok 101 is writable
ok 102 not readable
ok 103 is writable
ok 104 not readable
ok 105 is writable
ok 106 not readable
ok 107 is writable
ok 108 not readable
ok 109 is writable
ok 110 not readable
ok 111 is writable
ok 112 not readable
ok 113 is writable
ok 114 not readable
ok 115 is writable
ok 116 not readable
ok 117 is writable
ok 118 not readable
ok 119 is writable
ok 120 not readable
ok 121 is writable
ok 122 not readable
ok 123 not writable
ok 124 got expected error
ok 125 did not get value
ok 126 got expected error
ok 127 did not get value
ok 128 got expected error
ok 129 did not get value
ok 130 got expected error
ok 131 did not get value
ok 132 got expected error
ok 133 did not get value
ok 134 got expected error
ok 135 did not get value
ok 136 got expected error
ok 137 did not get value
ok 138 got expected error
ok 139 did not get value
ok 140 got expected error
ok 141 did not get value
ok 142 got expected error
ok 143 did not get value
# test json encoding
ok 144 no error
ok 145 no error
ok 146 not writable
ok 147 not readable
ok 148 no error
ok 149 WriteStream data #aa has correct value
ok 150 no error
ok 151 WriteStream data #ab has correct value
ok 152 no error
ok 153 WriteStream data #ac has correct value
ok 154 no error
ok 155 WriteStream data #ba has correct value
ok 156 no error
ok 157 WriteStream data #bb has correct value
ok 158 no error
ok 159 WriteStream data #bc has correct value
ok 160 no error
ok 161 WriteStream data #ca has correct value
ok 162 no error
ok 163 WriteStream data #cb has correct value
ok 164 no error
ok 165 WriteStream data #cc has correct value
# test del capabilities for each key/value
ok 166 no error
ok 167 no error
not ok 168 got expected error
  ---
    operator: ok
    expected: true
    actual:   null
  ...
not ok 169 did not get value
  ---
    operator: notOk
    expected: |-
      false
    actual: |-
      { a: 'complex', obj: 100 }
  ...
ok 170 got expected error
ok 171 did not get value
ok 172 got expected error
ok 173 did not get value
ok 174 got expected error
ok 175 did not get value
ok 176 got expected error
ok 177 did not get value
ok 178 got expected error
ok 179 did not get value
ok 180 got expected error
ok 181 did not get value
ok 182 got expected error
ok 183 did not get value
ok 184 got expected error
ok 185 did not get value
# test del capabilities as constructor option
ok 186 no error
ok 187 no error
ok 188 got expected error
ok 189 did not get value
ok 190 got expected error
ok 191 did not get value
ok 192 got expected error
ok 193 did not get value
ok 194 got expected error
ok 195 did not get value
ok 196 got expected error
ok 197 did not get value
ok 198 got expected error
ok 199 did not get value
ok 200 got expected error
ok 201 did not get value
ok 202 got expected error
ok 203 did not get value
ok 204 got expected error
ok 205 did not get value
# test type at key/value level must take precedence on the constructor
ok 206 no error
ok 207 no error
ok 208 got value
ok 209 got expected error
ok 210 did not get value
ok 211 got expected error
ok 212 did not get value
ok 213 got expected error
ok 214 did not get value
ok 215 got expected error
ok 216 did not get value
ok 217 got expected error
ok 218 did not get value
ok 219 got expected error
ok 220 did not get value
ok 221 got expected error
ok 222 did not get value
ok 223 got expected error
ok 224 did not get value
# test ignoring pairs with the wrong type
ok 225 no error
ok 226 no error
ok 227 got expected error
ok 228 did not get value
ok 229 got expected error
ok 230 did not get value
ok 231 got expected error
ok 232 did not get value
ok 233 got expected error
ok 234 did not get value
ok 235 got expected error
ok 236 did not get value
ok 237 got expected error
ok 238 did not get value
ok 239 got expected error
ok 240 did not get value
ok 241 got expected error
ok 242 did not get value
ok 243 got expected error
ok 244 did not get value
ok 245 got expected error
ok 246 did not get value

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.