		@@ -60,3 +60,2 @@ const JsonPointer = require("@hyperjump/json-pointer");

		const identity = (a) => a;
		const pipeline = (fns) => {
		@@ -72,8 +71,9 @@ const [handler = identity, ...handlers] = fns;
		const isId = (value) => isObject(value) && "$id" in value;
		const append = (key, doc) => "#" + encodeURI(JsonPointer.append(key, pointer(doc)));
		const append = (key, doc) => "#" + encodeURI(JsonPointer.append(key, pointer(doc))).replace(/#/g, "%23");
		const identity = (a) => a;

		module.exports = {
		contentType, contentTypeHandler,
		get, nil, source, value, pointer,
		entries, map, pipeline
		nil, source, get,
		value, pointer, entries, map, pipeline
		};

package.json

		{
		"name": "@hyperjump/browser",
		"version": "0.9.0",
		"version": "0.9.1",
		"description": "A generic hypermedia client for JSON Reference",
		@@ -28,3 +28,3 @@ "scripts": {
		"dependencies": {
		"@hyperjump/json-pointer": "^0.3.0",
		"@hyperjump/json-pointer": "^0.3.1",
		"bluebird": "^3.5.3",
		@@ -31,0 +31,0 @@ "just-curry-it": "^3.1.0",

README.md

		@@ -101,4 +101,3 @@ Hyperjump Browser
		JRef.get("#/eee"),
		JRef.map(JRef.value),
		(items) => items.map((a) => a * 2)
		JRef.map((items) => JRef.value(items) * 2)
		]);
		@@ -121,6 +120,7 @@ await doubleEee(doc); // => [666, 222]

		With this implementation, I use JSON Reference draft-03 from the original
		authors as a starting point and evolve the concept from there. Therefore, this
		implementation IS NOT the same JSON Reference used in recent drafts of JSON
		Schema.
		With this implementation, I use
		[JSON Reference draft-03](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03)
		from the original authors as a starting point and evolve the concept from there.
		Therefore, _the `$ref` and `$id` in this implementation IS NOT the same `$ref`
		and `$id` used in recent drafts of JSON Schema_.

		@@ -127,0 +127,0 @@ Documentation

@hyperjump/browser - npm Package Compare versions

New alerts