profile
viewpoint
Austin Wright awwright Arizona https://twitter.com/awwscript Just this guy, you know?

awwright/magnode 22

The semantic content management system for Node.js.

awwright/contenttype 8

Javascript/ECMAScript library for parsing Content-Type and Media/MIME type strings

awwright/http-progress 8

Resumable Requests and Long-Running Operations in HTTP

awwright/git-node 5

Make Node.js submodules useful

awwright/dive-httpd 3

Experimental HTTP application framework based on URI templates and Stream#pipe

awwright/jsonschemaparse 3

Streaming parser for JSON with automatic validation and customizable parsing

awwright/json-metaschema 2

Meta-schemas for JSON Schema

awwright/jsonschema 2

jsonschema

awwright/CAPSLOCKSCRIPT 1

JAVASCRIPT, LOUD, STRONG AND IMPROVED

awwright/grammartool 1

Parse an ABNF/EBNF and test it against streams of input

push eventtdegrunt/jsonschema

Austin Wright

commit sha 8f71ba6fe1462d3930a9f11b67c12cae5d0006f5

Test "pattern" keyword with unicode flag

view details

push time in 10 hours

push eventawwright/jsonschemaparse

Austin Wright

commit sha 8db35938dfbfbe17722bda407cc24ef63b07ea22

Refactor ValidateLayer#initProperty

view details

Austin Wright

commit sha 4a7a835c4a61654d4c360155f7b082067c69b523

Refactor "required" to use Set

view details

Austin Wright

commit sha 441752d332dcd3f699db43a21775439fb2267f79

Refactor ResourceLimitError

view details

Austin Wright

commit sha 265ee405c0ae80b75c234c46a38d5c9b955e80d6

Fix ResourceLimitError

view details

Austin Wright

commit sha 7f99c5b1b9a2e778c10ee7fc0ca77958c73db4cf

Add ValidateLayer#evaluatedPropertiesSet

view details

Austin Wright

commit sha 3768056cd635ce720542cc33325922c17ea77bde

Also import evaluated properties from allOf

view details

Austin Wright

commit sha e7ff3ae6064d5dd1df832b1a5f4d93a543af0c38

unevaluatedProperties: getting closer

view details

Austin Wright

commit sha c38a7c1bb7bdf36e96cf9bf7e213333714a82598

gh-pages build

view details

push time in 20 hours

issue commentjson-schema-org/json-schema-spec

Extend the specification to define a license property, so that IP considerations are unambiguous, and it is addressed consistently.

I don't think this makes sense.

There is nothing about this that is specific to JSON Schema, and any solution we come up with, I think you should be able to use to describe other documents, too. I think data like this is better expressed with something more standard, like the rel=license link relation. Or perhaps a JSON Schema defines a keyword equivalent to an HTML meta tag.

Also I think licensing is a legal concept, and technical standards do not set the law. And in the US, APIs and data are not necessarily copyrightable. The contents of a book might be copyrighted; but the fact the book is divided into chapters and each chapter has one heading and 0+ paragraphs and so on—this is just expressing a fact about how books are written; likewise, JSON Schema is merely expressing facts about how JSON documents are formed. So I think the presence of a "license" property could be misleading.

ericjohnson-tibco

comment created time in 21 hours

push eventawwright/jsonschemaparse

Austin Wright

commit sha 441752d332dcd3f699db43a21775439fb2267f79

Refactor ResourceLimitError

view details

Austin Wright

commit sha 265ee405c0ae80b75c234c46a38d5c9b955e80d6

Fix ResourceLimitError

view details

Austin Wright

commit sha 7f99c5b1b9a2e778c10ee7fc0ca77958c73db4cf

Add ValidateLayer#evaluatedPropertiesSet

view details

Austin Wright

commit sha 3768056cd635ce720542cc33325922c17ea77bde

Also import evaluated properties from allOf

view details

Austin Wright

commit sha e7ff3ae6064d5dd1df832b1a5f4d93a543af0c38

unevaluatedProperties: getting closer

view details

push time in 21 hours

push eventawwright/jsonschemaparse

Austin Wright

commit sha 4a7a835c4a61654d4c360155f7b082067c69b523

Refactor "required" to use Set

view details

push time in 2 days

push eventfullstackwiki/fullstackwiki

Austin Wright

commit sha 96500a4e2b5469c0def9e2a2178ebaaa8edbbb7f

Rework 404 status code page

view details

push time in 3 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 8db35938dfbfbe17722bda407cc24ef63b07ea22

Refactor ValidateLayer#initProperty

view details

push time in 3 days

issue commentnodejs/web-server-frameworks

Returning a `res` object

@wesleytodd I don't think that's really the same thing; I'm not proposing a change in the public API except maybe for how streams works

awwright

comment created time in 5 days

pull request commentawwright/uri-template-router

Provide a route.toJSON() to print the template URI

@Lcfvs Dropped 0.0.12 for you

Lcfvs

comment created time in 5 days

created tagawwright/uri-template-router

tagv0.0.12

Match a URI to a template from a collection of URI Templates

created time in 5 days

push eventawwright/uri-template-router

Austin Wright

commit sha ed6d5014404c9ac9edd0d462a71c436230c6a6e2

gh-pages build

view details

push time in 7 days

push eventawwright/uri-template-router

Austin Wright

commit sha f83804d7209975a2372d66e4b505ceef77fdd840

docs: Fix some titles

view details

push time in 7 days

pull request commentawwright/uri-template-router

Provide a route.toJSON() to print the template URI

@Lcfvs Do you want a packaged release?

Lcfvs

comment created time in 7 days

PR merged awwright/uri-template-router

Provide a route.toJSON() to print the template URI

Hi @awwright :)

Would it be fine for you?

+3 -0

1 comment

1 changed file

Lcfvs

pr closed time in 7 days

push eventawwright/uri-template-router

Lcf.vs

commit sha 1fc3ae46865ed82ad3e212ab15e7cf104aa06e2c

Provide a route.toJSON() to print the template URI

view details

Austin Wright

commit sha 561b585d92f7cd3fcbad615f743319ce1310ccbd

Merge pull request #4 from Lcfvs/patch-1 Provide a route.toJSON() to print the template URI

view details

push time in 7 days

pull request commentawwright/uri-template-router

Provide a route.toJSON() to print the template URI

Yeah that seems reasonable

Lcfvs

comment created time in 7 days

issue openednodejs/web-server-frameworks

Returning a `res` object

This is related to a comment I left on a gist that was posted somewhere here; I'm interested in the ability to return a ServerResponse object, instead of using a created one. I have a library, http-transform, that allows you to do this (more-or-less, see below).

An upside to this is it lets you use pipe(), a downside is you don't know the capabilities of the receiving end (if it's HTTP/1.1, HTTP/2, etc). However, that responses use completely generic HTTP semantics instead of encoding-specific semantics could itself be seen as an upshot in some cases.

This is likely a poor way to do all Node.js HTTP responses, but it seems to me a framework should be able to do things this way.

I'm looking to discuss some of the limitations of Node.js that make this difficult, like in the http and stream modules. Is this a good topic for discussion?

created time in 7 days

PR closed xmldom/xmldom

Port custom assertions to mostly strict assertions

I'd like to start chipping away at converting the test suite, I've converted a Vows suite to Mocha before. This one looks pretty straightforward, actually.

I think the first logical step here is to start with the assertions themselves, and use the Node.js core library and only the builtin functions.

In particular, assert.isTrue is a monkey-patch by Vows. I found most all the tests can use assert.strictEqual. There's a few that test if an object is cast to a string, these use assert.equal. There's two more that I think don't meet the DOM standard if you use ===, these use assert.equal and are marked with a FIXME.

+209 -493

17 comments

23 changed files

awwright

pr closed time in 8 days

pull request commentxmldom/xmldom

Port custom assertions to mostly strict assertions

I mean, I'm not sure what else to say... GitHub doesn't show any history, but it shows my rebases and commits that I pushed, and I see you mentioning this from other PRs, but it doesn't show any commits pushed to my branch.

awwright

comment created time in 8 days

pull request commentxmldom/xmldom

Port custom assertions to mostly strict assertions

@brodybits Well, OK, but I'm trying to figure out what changes you're talking about, do you mean a PR? I'm curious which errors you're referring to.

awwright

comment created time in 8 days

pull request commentxmldom/xmldom

Port custom assertions to mostly strict assertions

@brodybits I'm sorry, when was that? Was this PR introducing build errors?

awwright

comment created time in 8 days

pull request commentxmldom/xmldom

Port custom assertions to mostly strict assertions

I was proposing that, after the code is formatted, to first port the assertion calls (as in this PR). That would make changing over the test runner a minimal amount of effort. Then working on fixing tests and adding coverage.

...it seems the test runner has mostly been converted, though.

I favor using assert. It's simple and straightforward.

awwright

comment created time in 8 days

push eventawwright/xmldom

Austin Wright

commit sha ce6f144cd031f2dc1f872a307ae37f3a2d4c1f98

Convert Vows assertions to Node.js assertion library

view details

push time in 8 days

push eventawwright/xmldom

Austin Wright

commit sha be92b95e3d39e0fb43dff0d029942f4754606719

Convert Vows assertions to Node.js assertion library

view details

push time in 8 days

push eventawwright/xmldom

Austin Wright

commit sha 8c80c8cd021eda139403d9e5be3623f0f06328df

Convert Vows assertions to Node.js assertion library

view details

push time in 8 days

push eventawwright/xmldom

Austin Wright

commit sha bbe94fcbbecdbe984c051cd021f828171edb5955

Convert Vows assertions to Node.js assertion library

view details

push time in 8 days

push eventawwright/xmldom

Austin Wright

commit sha 3bf072790793ec5a7a738c167a14be73526b30a1

Convert Vows assertions to Node.js assertion library

view details

push time in 8 days

PR closed xmldom/xmldom

Lint with tabs & enable strict mode bug

This adds an .eslintrc.js, .editorconfig, and normalizes the whitespace to 1-tab indents.

Btw, whitespace can be ignored from GitHub by adding ?w=1 to a diff URL: https://github.com/xmldom/xmldom/pull/90/commits/2bbb7e2459abc64f7270f5f08eab8d8022137f96?w=1

This is mostly just a suggestion, it's easy enough to go with a different style if something else is more popular.

After this:

  • [ ] Fix remaining eslint errors with switch/break statements
  • [ ] Add eslint to CI tests
  • [ ] Enable additional eslint tests
+436 -405

8 comments

5 changed files

awwright

pr closed time in 8 days

push eventawwright/xmldom

Chris Brody

commit sha 7a8814ce92961e14e7cfba14aad3009e8dc62b90

enable & enforce strict mode in test modules (#124) Co-authored-by: Austin Wright <aaa@bzfx.net>

view details

push time in 8 days

push eventawwright/xmldom

Austin Wright

commit sha 84e4d44f2007f0291bd0806abaf3c9409dc6e145

Convert Vows assertions to Node.js assertion library

view details

push time in 8 days

PullRequestReviewEvent

issue commentxmldom/xmldom

Improve test coverage with future-proof testing strategy

The next thing I would like too see is the formatting.

Like if we could get a PR focused only on normalizing the whitespace, that would be great.

karfau

comment created time in 9 days

pull request commentxmldom/xmldom

Convert custom assertions to strict assertions

I rebased over the updates from #121.

awwright

comment created time in 9 days

push eventawwright/xmldom

dependabot[bot]

commit sha 0b2808aca7463d12bd7b3ff459afbe93cbb710bf

Bump lodash from 4.17.15 to 4.17.19 (#94) Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.15...4.17.19) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

Rolf Grossmann

commit sha 66db3e4a0c160d684828eab8cbaa2f1848322d6f

remove ES6 syntax from getElementsByClassName (#91)

view details

Christian Bewernitz

commit sha 58844cddcba8907791a0edb485cfef5310a16387

test: Restructure & improve npm test scripts (#87) Tests for `test/assert.js` need to run before the vows test suite, not as part of them. - Rename `test/assert.vows.js` to `test/assert.vows.checks.js` - Script `test:assert` only runs those tests - Script `test:assert:strict` runs them with strict assertions - Script `test:unit` and `test:vows` are currently the same (until we add another testing framework to the mix) - Update script `test` to run strict assertions only on `test/assert.vows.checks.js` In the end `npm [run] test` executes the same amount of tests on CI but it's more easy to run a subset. Added devDependency [`npm-run-all`](https://www.npmjs.com/package/npm-run-all) https://github.com/xmldom/xmldom/issues/82 https://github.com/xmldom/xmldom/pull/77#issuecomment-652690183 Co-authored-by: Christian Bewernitz <coder@karfau.de> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com>

view details

Chris Brody

commit sha 3ceec5ee70f768044868847f380f9fa37ecead2d

Add .editorconfig file (#104) as originally proposed in PR #90 Co-authored-by: Austin Wright <aaa@bzfx.net> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com>

view details

renovate[bot]

commit sha b935c84a82fbd9c80062148007069f0e3c867812

Configure Renovate (#108) * chore(deps): add renovate.json * add "rangeStrategy": "bump" ref: https://docs.renovatebot.com/configuration-options/#rangestrategy * customize commitMessageExtra based on: https://docs.renovatebot.com/configuration-options/#commitmessageextra * terse commitMessageTopic * add ":semanticCommitsDisabled" to extends to keep the PR title & commit message topic terse ref: https://docs.renovatebot.com/semantic-commits/ * additional settings in extends list * add "prHourlyLimit": 0 setting Co-authored-by: Renovate Bot <bot@renovateapp.com> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com> Co-authored-by: Eric Newport <kethinov@gmail.com>

view details

renovate[bot]

commit sha 65a7220af08e26cdc9cd03ac2c63beaa9dbcef5c

Update stryker monorepo -> ^3.3.1 - devDependencies (#109) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

Christian Bewernitz

commit sha 4dd45a4b250d90844b57d88718e19c6abea4f765

Reduce time needed for stryker (#105) By not running the tests in `test/assert.js`, we can reduce the duration of the stryker run by a small portion. They shouldn't change the result since they are only test helpers that don't change how the actual code is tested. Committed-by: Chris Brody <chris.brody+brodybits@gmail.com> via GitHub

view details

Chris Brody

commit sha fd030ee673374908a16e18498dba95bcac5a1e9b

add & enable eslint (#106) * add eslint to devDependencies * start custom .eslintrc.yml with help from `npx eslint --init` * add (es)lint entries to package scripts * add lint to end of test script * comment out most .eslintrc.yml entries for now

view details

Chris Brody

commit sha 3609c88fed4641f00f572365d64edb7042772735

use eslint-plugin-es5 to enforce ES5 (#107) should guard against newer ES6 syntax that could lead to issues with some ES5 environments such as: - Jint - https://github.com/sebastienros/jint - Duktape - IE11 - Android pre-5.0 WebView (already past EOL) as discussed in PR #91 - https://github.com/xmldom/xmldom/pull/91

view details

jesse-y

commit sha bd81fab4f0df48840f9834fdce5fd475510168fa

fix: typecheck source param before parsing (#113)

view details

Christian Bewernitz

commit sha 4cf7840c32f10fe8726ce0fd0d69b840283bf605

test: Add jest and first tests (#114) * test: Add jest and first tests * test: remove coverage options from jest config * test: Consistent naming and ordering of npm scripts * test: Verify access to textContent and attributes (#93)

view details

renovate[bot]

commit sha 8146222c1b0c2e9cdb153e29d0f9d7bbbdc69f9a

Update eslint -> ^7.8.1 - devDependencies (#115) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

renovate[bot]

commit sha 766fbdea84cf1843186fd2d2558c74ad6fb77931

Update eslint -> ^7.9.0 - devDependencies (#118) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

Christian Bewernitz

commit sha 581ad93b827522f0434b513317e7a25df94a8bff

test: Add jest testsuite with `xmltest` cases (#112) The only thing the current test suite does is to run tons of cases and take a snapshot of the output and errors, so that hopefully a test will fail if we make a breaking change. (It doesn't cover breaking API changes of course, but sets the basis and any added test will be part of CI testing.) Add devDependencies: - npm.im/xmltest from https://github.com/karfau/xmltest & it's peerDependencies: - npm.im/get-stream - npm.im/yauzl Add new helper module `test/get-test-parser.js`: To simplify the very common use case of testing DOMParser results Co-authored-by: Christopher J. Brody <chris.brody+brodybits@gmail.com>

view details

Chris Brody

commit sha 193fc0058362cfc70dc376a82ccfe75925e32638

Port Vows tests to Jest & remove test:vows script (#121)

view details

Chris Brody

commit sha f8acd2af2507879c3bcf432fc581d7d9ab682cce

fix HTML normalize test (#122)

view details

Austin Wright

commit sha 3c762e6c8c34ee41bd908b79ab852cd18ffe9b26

Declare "use strict" on tests

view details

Austin Wright

commit sha 3081e0873aee2056ab805dc917785cf92080425c

Convert Vows assertions to Node.js assertion library

view details

push time in 9 days

push eventawwright/xmldom

dependabot[bot]

commit sha 0b2808aca7463d12bd7b3ff459afbe93cbb710bf

Bump lodash from 4.17.15 to 4.17.19 (#94) Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.15...4.17.19) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

Rolf Grossmann

commit sha 66db3e4a0c160d684828eab8cbaa2f1848322d6f

remove ES6 syntax from getElementsByClassName (#91)

view details

Christian Bewernitz

commit sha 58844cddcba8907791a0edb485cfef5310a16387

test: Restructure & improve npm test scripts (#87) Tests for `test/assert.js` need to run before the vows test suite, not as part of them. - Rename `test/assert.vows.js` to `test/assert.vows.checks.js` - Script `test:assert` only runs those tests - Script `test:assert:strict` runs them with strict assertions - Script `test:unit` and `test:vows` are currently the same (until we add another testing framework to the mix) - Update script `test` to run strict assertions only on `test/assert.vows.checks.js` In the end `npm [run] test` executes the same amount of tests on CI but it's more easy to run a subset. Added devDependency [`npm-run-all`](https://www.npmjs.com/package/npm-run-all) https://github.com/xmldom/xmldom/issues/82 https://github.com/xmldom/xmldom/pull/77#issuecomment-652690183 Co-authored-by: Christian Bewernitz <coder@karfau.de> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com>

view details

Chris Brody

commit sha 3ceec5ee70f768044868847f380f9fa37ecead2d

Add .editorconfig file (#104) as originally proposed in PR #90 Co-authored-by: Austin Wright <aaa@bzfx.net> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com>

view details

renovate[bot]

commit sha b935c84a82fbd9c80062148007069f0e3c867812

Configure Renovate (#108) * chore(deps): add renovate.json * add "rangeStrategy": "bump" ref: https://docs.renovatebot.com/configuration-options/#rangestrategy * customize commitMessageExtra based on: https://docs.renovatebot.com/configuration-options/#commitmessageextra * terse commitMessageTopic * add ":semanticCommitsDisabled" to extends to keep the PR title & commit message topic terse ref: https://docs.renovatebot.com/semantic-commits/ * additional settings in extends list * add "prHourlyLimit": 0 setting Co-authored-by: Renovate Bot <bot@renovateapp.com> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com> Co-authored-by: Eric Newport <kethinov@gmail.com>

view details

renovate[bot]

commit sha 65a7220af08e26cdc9cd03ac2c63beaa9dbcef5c

Update stryker monorepo -> ^3.3.1 - devDependencies (#109) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

Christian Bewernitz

commit sha 4dd45a4b250d90844b57d88718e19c6abea4f765

Reduce time needed for stryker (#105) By not running the tests in `test/assert.js`, we can reduce the duration of the stryker run by a small portion. They shouldn't change the result since they are only test helpers that don't change how the actual code is tested. Committed-by: Chris Brody <chris.brody+brodybits@gmail.com> via GitHub

view details

Chris Brody

commit sha fd030ee673374908a16e18498dba95bcac5a1e9b

add & enable eslint (#106) * add eslint to devDependencies * start custom .eslintrc.yml with help from `npx eslint --init` * add (es)lint entries to package scripts * add lint to end of test script * comment out most .eslintrc.yml entries for now

view details

Chris Brody

commit sha 3609c88fed4641f00f572365d64edb7042772735

use eslint-plugin-es5 to enforce ES5 (#107) should guard against newer ES6 syntax that could lead to issues with some ES5 environments such as: - Jint - https://github.com/sebastienros/jint - Duktape - IE11 - Android pre-5.0 WebView (already past EOL) as discussed in PR #91 - https://github.com/xmldom/xmldom/pull/91

view details

jesse-y

commit sha bd81fab4f0df48840f9834fdce5fd475510168fa

fix: typecheck source param before parsing (#113)

view details

Christian Bewernitz

commit sha 4cf7840c32f10fe8726ce0fd0d69b840283bf605

test: Add jest and first tests (#114) * test: Add jest and first tests * test: remove coverage options from jest config * test: Consistent naming and ordering of npm scripts * test: Verify access to textContent and attributes (#93)

view details

renovate[bot]

commit sha 8146222c1b0c2e9cdb153e29d0f9d7bbbdc69f9a

Update eslint -> ^7.8.1 - devDependencies (#115) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

renovate[bot]

commit sha 766fbdea84cf1843186fd2d2558c74ad6fb77931

Update eslint -> ^7.9.0 - devDependencies (#118) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

Christian Bewernitz

commit sha 581ad93b827522f0434b513317e7a25df94a8bff

test: Add jest testsuite with `xmltest` cases (#112) The only thing the current test suite does is to run tons of cases and take a snapshot of the output and errors, so that hopefully a test will fail if we make a breaking change. (It doesn't cover breaking API changes of course, but sets the basis and any added test will be part of CI testing.) Add devDependencies: - npm.im/xmltest from https://github.com/karfau/xmltest & it's peerDependencies: - npm.im/get-stream - npm.im/yauzl Add new helper module `test/get-test-parser.js`: To simplify the very common use case of testing DOMParser results Co-authored-by: Christopher J. Brody <chris.brody+brodybits@gmail.com>

view details

Chris Brody

commit sha 193fc0058362cfc70dc376a82ccfe75925e32638

Port Vows tests to Jest & remove test:vows script (#121)

view details

Chris Brody

commit sha f8acd2af2507879c3bcf432fc581d7d9ab682cce

fix HTML normalize test (#122)

view details

Austin Wright

commit sha 3c762e6c8c34ee41bd908b79ab852cd18ffe9b26

Declare "use strict" on tests

view details

Austin Wright

commit sha 3081e0873aee2056ab805dc917785cf92080425c

Convert Vows assertions to Node.js assertion library

view details

push time in 9 days

push eventawwright/xmldom

dependabot[bot]

commit sha 0b2808aca7463d12bd7b3ff459afbe93cbb710bf

Bump lodash from 4.17.15 to 4.17.19 (#94) Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19. - [Release notes](https://github.com/lodash/lodash/releases) - [Commits](https://github.com/lodash/lodash/compare/4.17.15...4.17.19) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

view details

Rolf Grossmann

commit sha 66db3e4a0c160d684828eab8cbaa2f1848322d6f

remove ES6 syntax from getElementsByClassName (#91)

view details

Christian Bewernitz

commit sha 58844cddcba8907791a0edb485cfef5310a16387

test: Restructure & improve npm test scripts (#87) Tests for `test/assert.js` need to run before the vows test suite, not as part of them. - Rename `test/assert.vows.js` to `test/assert.vows.checks.js` - Script `test:assert` only runs those tests - Script `test:assert:strict` runs them with strict assertions - Script `test:unit` and `test:vows` are currently the same (until we add another testing framework to the mix) - Update script `test` to run strict assertions only on `test/assert.vows.checks.js` In the end `npm [run] test` executes the same amount of tests on CI but it's more easy to run a subset. Added devDependency [`npm-run-all`](https://www.npmjs.com/package/npm-run-all) https://github.com/xmldom/xmldom/issues/82 https://github.com/xmldom/xmldom/pull/77#issuecomment-652690183 Co-authored-by: Christian Bewernitz <coder@karfau.de> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com>

view details

Chris Brody

commit sha 3ceec5ee70f768044868847f380f9fa37ecead2d

Add .editorconfig file (#104) as originally proposed in PR #90 Co-authored-by: Austin Wright <aaa@bzfx.net> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com>

view details

renovate[bot]

commit sha b935c84a82fbd9c80062148007069f0e3c867812

Configure Renovate (#108) * chore(deps): add renovate.json * add "rangeStrategy": "bump" ref: https://docs.renovatebot.com/configuration-options/#rangestrategy * customize commitMessageExtra based on: https://docs.renovatebot.com/configuration-options/#commitmessageextra * terse commitMessageTopic * add ":semanticCommitsDisabled" to extends to keep the PR title & commit message topic terse ref: https://docs.renovatebot.com/semantic-commits/ * additional settings in extends list * add "prHourlyLimit": 0 setting Co-authored-by: Renovate Bot <bot@renovateapp.com> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com> Co-authored-by: Eric Newport <kethinov@gmail.com>

view details

renovate[bot]

commit sha 65a7220af08e26cdc9cd03ac2c63beaa9dbcef5c

Update stryker monorepo -> ^3.3.1 - devDependencies (#109) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

Christian Bewernitz

commit sha 4dd45a4b250d90844b57d88718e19c6abea4f765

Reduce time needed for stryker (#105) By not running the tests in `test/assert.js`, we can reduce the duration of the stryker run by a small portion. They shouldn't change the result since they are only test helpers that don't change how the actual code is tested. Committed-by: Chris Brody <chris.brody+brodybits@gmail.com> via GitHub

view details

Chris Brody

commit sha fd030ee673374908a16e18498dba95bcac5a1e9b

add & enable eslint (#106) * add eslint to devDependencies * start custom .eslintrc.yml with help from `npx eslint --init` * add (es)lint entries to package scripts * add lint to end of test script * comment out most .eslintrc.yml entries for now

view details

Chris Brody

commit sha 3609c88fed4641f00f572365d64edb7042772735

use eslint-plugin-es5 to enforce ES5 (#107) should guard against newer ES6 syntax that could lead to issues with some ES5 environments such as: - Jint - https://github.com/sebastienros/jint - Duktape - IE11 - Android pre-5.0 WebView (already past EOL) as discussed in PR #91 - https://github.com/xmldom/xmldom/pull/91

view details

jesse-y

commit sha bd81fab4f0df48840f9834fdce5fd475510168fa

fix: typecheck source param before parsing (#113)

view details

Christian Bewernitz

commit sha 4cf7840c32f10fe8726ce0fd0d69b840283bf605

test: Add jest and first tests (#114) * test: Add jest and first tests * test: remove coverage options from jest config * test: Consistent naming and ordering of npm scripts * test: Verify access to textContent and attributes (#93)

view details

renovate[bot]

commit sha 8146222c1b0c2e9cdb153e29d0f9d7bbbdc69f9a

Update eslint -> ^7.8.1 - devDependencies (#115) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

renovate[bot]

commit sha 766fbdea84cf1843186fd2d2558c74ad6fb77931

Update eslint -> ^7.9.0 - devDependencies (#118) Co-authored-by: Renovate Bot <bot@renovateapp.com>

view details

Christian Bewernitz

commit sha 581ad93b827522f0434b513317e7a25df94a8bff

test: Add jest testsuite with `xmltest` cases (#112) The only thing the current test suite does is to run tons of cases and take a snapshot of the output and errors, so that hopefully a test will fail if we make a breaking change. (It doesn't cover breaking API changes of course, but sets the basis and any added test will be part of CI testing.) Add devDependencies: - npm.im/xmltest from https://github.com/karfau/xmltest & it's peerDependencies: - npm.im/get-stream - npm.im/yauzl Add new helper module `test/get-test-parser.js`: To simplify the very common use case of testing DOMParser results Co-authored-by: Christopher J. Brody <chris.brody+brodybits@gmail.com>

view details

Chris Brody

commit sha 193fc0058362cfc70dc376a82ccfe75925e32638

Port Vows tests to Jest & remove test:vows script (#121)

view details

Chris Brody

commit sha f8acd2af2507879c3bcf432fc581d7d9ab682cce

fix HTML normalize test (#122)

view details

Austin Wright

commit sha 292fd345f8f5f20ab8dce07649f85ae0406e2f91

Add .eslintrc.js

view details

Austin Wright

commit sha 86cdabb263cd416b200ab5c691d886c2f3b6089e

Appease linter: normalize whitespace

view details

push time in 9 days

push eventawwright/json-schema-org.github.io

Austin Wright

commit sha 78e85b53b53606c8fe4048014c3045b03bc3bfbb

Update index.md Co-authored-by: Ben Hutton <relequestual@gmail.com>

view details

push time in 10 days

PR opened json-schema-org/json-schema-org.github.io

Make spec links more obvious

This moves the specification links closer to the top, to hopefully be seen without scrolling.

This also removes "New Draft" notice which is about a year old now.

This further removes the "Draft numbering" section, because it seems to already be explained on the "specification links" page.

+2 -20

0 comment

2 changed files

pr created time in 11 days

push eventawwright/json-schema-org.github.io

Adam Quaile

commit sha 1d9a3afe34525c3b792c0f1366abf914ea2e242a

Use HTTPS for schema links

view details

Jess Lee Yarbrough

commit sha 1bdb6f9039452586b90faa02788490190948f04f

Update implementations.md with Go validator benchmarks

view details

Peter Urbak

commit sha 454968f5e78b6680e702a687d428f12f5b32b83a

Adds link to json-schema-to-elm

view details

ldexterldesign

commit sha d76fe783d7827da6a711230b2e52fada60499a0b

Add https://github.com/json-schema-faker to generator (i.e. data) from schema

view details

leadpony

commit sha ee4f29823604f02186721aa05d99b0897c7669a7

Update the supported drafts for Justify

view details

Alexander Falk

commit sha 7d638dd97866881f11b4c6682725a5db63811413

Added Altova XMLSpy 2019r3 to list of Editors Added Altova XMLSpy 2019r3 to list of Editors, since it now supports draft-06 and draft-07 of JSON Schema

view details

Henrik Mohr

commit sha f97f722ec00f80e882ee7d505103552b5c337c92

Update of license for Clojure library

view details

Sander Hahn

commit sha 1dd92ac9be1c292a424e828083cc51f39631652d

example $id update

view details

Johan Dorland

commit sha 3e6d2485d34d405212247119a91ab169c22ba35d

Fix a spelling error on the WIP page

view details

Ben Hutton

commit sha 405ef043f7c5ae7db716271a3d83507e3a51e4e8

Merge pull request #274 from johandorland/master Fix a spelling error on the WIP page

view details

Ben Hutton

commit sha 3aeb9ffc46eb3f9060b87e06d86cb84aca0a453c

Fix issue badges! Sorry!

view details

Carsten Wickner

commit sha 88ddacd7448f43198226036a2a7813c4e8c834d7

Include Java-from-Code schema generator example

view details

Relequestual

commit sha ac82756864d044ac210f52b07d1ee129982d9aca

Update WIP docs

view details

Relequestual

commit sha 0f4d12a2650613a77c760c6bf658061430eb6e19

Merge branch 'new-files'

view details

Drew Miller

commit sha 38a663fb5fc4f505aed42da90684a68d4b2a671a

Remove projects with dead links

view details

Phil Sturgeon

commit sha eff9cf489aca4daa1ac91119aa6a07eacc5d858b

Merge pull request #277 from millerdrew/patch-1 Remove projects with dead links

view details

Thomas Schulz

commit sha a0ebcf59e39f1f38fd0885f419a73fb2f3bf76bf

Add info about YAML support in IntelliJ based IDEs

view details

Ben Hutton

commit sha 35b1d4afe336b67a71b1ce7ead5fa6b4aa5e40a2

Merge pull request #280 from King2500/patch-1 Added info about YAML support in IntelliJ based IDEs

view details

Julian Berman

commit sha 39e0fed7e7f829e81e58a9f93a01ab8c69b20ebc

Merge pull request #268 from leadpony/update-validator-list Update the supported drafts for Justify

view details

Henry Andrews

commit sha 1412d61c8b479abf857699749117d2d9fe33c4a7

Update on draft review timeline.

view details

push time in 11 days

push eventawwright/uri-template-router

Austin Wright

commit sha df82f5decd914994f3e9cbddb38910ab7cf7d21d

Add gh-pages publishing script

view details

Austin Wright

commit sha 7711241f3b7de4419b9dffb0200a6104e4c82b91

Add Router#resolveRequestURI function

view details

Austin Wright

commit sha 22f511a9bc21ece49aa1e2654bbb7372d49e1bf8

docs: Update style

view details

Austin Wright

commit sha c54e2fba5e82cd023831a19c8eb974238ce31dfe

gh-pages build

view details

push time in 11 days

push eventawwright/uri-template-router

Austin Wright

commit sha 22f511a9bc21ece49aa1e2654bbb7372d49e1bf8

docs: Update style

view details

push time in 11 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha d94b32895e1713846213432213df3071eef64cd8

Update website

view details

Austin Wright

commit sha 96d3b3beef1f86f692c42cadf38045f011f3ab7b

Remove Schema#parse methods This just makes the interface more consistent and lays the way to have parsers other than JSON

view details

Austin Wright

commit sha 791f06f68807a936cfbf6c0b9431f1dded75850f

Rename mocha tests to end in .test.js

view details

Austin Wright

commit sha ef64265de414fd44e129d4078a5195116801b211

Add performance testing tools

view details

Austin Wright

commit sha ae6b1d5b0b2a135b4ee2eacfe7b5917e0230b1d6

Fix tests I'm not sure how these broke but by all indications they shouldn't

view details

Austin Wright

commit sha 3f56a31dbec1f14ba8fc7948677ae6725b958022

Update for GitHub Pages

view details

Austin Wright

commit sha 809cba2787e72307d7f55ad2ee37edcd0c6aed86

Fix website build

view details

Austin Wright

commit sha c4c49a2f50aa6fd4b681f9ab2902b74ca20f3ad1

Update dark mode colors

view details

Austin Wright

commit sha 35da8409465c658d75785b81a6d3904c0e27f9ad

docs: Typos

view details

Austin Wright

commit sha 79f3fcdb5816dd6457f8fda6b627c2e36942db47

docs: Add streaming example

view details

Austin Wright

commit sha 9443fbfb2c4c086a1653fffa398e34f1d96cca89

docs: Lint the schema too

view details

Austin Wright

commit sha 95dd4351e6f74083741e5534958c7e5a5a9f5f6c

Ignore website build products

view details

Austin Wright

commit sha c6d75b53bcf692f62ed6cd43df900c728057993e

Move Schema/SchemaRegistry tests to separate file

view details

Austin Wright

commit sha fe6dbdf161721c9b7bdb5974b13071e4dfdb6fc9

Add support for unevaluatedProperties There has to be something wrong here, all the tests pass with only a few lines of code

view details

Austin Wright

commit sha 3951edc328768f64616593f947a14b6b229306e0

Test for expected module interface in interface.test.js

view details

Austin Wright

commit sha 28e4d29af323fcbdfdffb7f2b8dc64f22f6afb44

Split apart tests by function

view details

Austin Wright

commit sha fe2fbbe58030a8df5521ddaf2d976679f285a0e1

Add Stryker for testing

view details

Austin Wright

commit sha e69a47378edd613375841f12f0e092db3829103a

Allow parseInfo(text, schema) form

view details

Austin Wright

commit sha 2aa19231bdda03aac96343f5b61503b147633b52

Add tests

view details

Austin Wright

commit sha 529ff4e94fd00a9a9254a543999ceb511cd47204

Tests for numbers and strings

view details

push time in 11 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha c6343809b67aa8089d36fa4d855a41b0e8a61bc6

Implement Schema#references, Schema#allReferences

view details

push time in 12 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 5b3be29529382f4b96ba0b26b83f80b99c99dc87

Add Schema#subschemas, Schema#allSchemas, Schema#allUnknown

view details

push time in 13 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 8e591e2464945265a0f4bf3e39ada91152640c60

Test values of "type" keyword

view details

push time in 14 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha f5ea5bd7d0c0c9f43356b90ddb7c5d87a23455c2

README: Remove "Migrating" section, it's in the documentation

view details

push time in 14 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 2e661053b377d7d1b8070edd2ed6abbcdf1fa73f

Supress unevaluatedProperties tests until it's implemented

view details

Austin Wright

commit sha 4952faaaa052208b3f7fea14fa516b60c531ab1f

Add ResourceLimitError

view details

push time in 15 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 5bc906c98530c678580df8b6585ad83326c953b9

Expose Annotation constructor

view details

push time in 15 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha af101cd885f0911057f8631d8bcc1750b8465ff1

Add tests for SyntaxError, ValidationError, Annotation

view details

push time in 15 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha a0f1a82eb39e240d4e80c5ddb1aba3f0612e9050

Test additional boundaries

view details

push time in 15 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha b1009ef65e8322cd9bf1b6f464df802e99def02a

Add test for if/then/else domain

view details

push time in 15 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 7b44f6d8cf6dfc837550d984ba4e0a648befb1b9

Add tests for object/array

view details

push time in 15 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha d41d7ab20587b29c2541727eeae1db15cfebe9ec

Add more validation tests

view details

Austin Wright

commit sha 37cb91f0ff6c7bbbf65d01cc330a70f69b85451b

docs: Describe the three paradigms

view details

Austin Wright

commit sha 20015ef5ef4084313a16b5010deec76eb63324e1

More tests

view details

push time in 15 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 507ae967b8f3d58fa2262fde6ab6bd3adb0b11ba

Add some tests for domain of recognised schema keywords

view details

push time in 16 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha cb00b472607291dbdbcba441ffc8112778073049

Tests for max parse length

view details

push time in 16 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 3a2ed0a31b07e9fcfcfcadaf639419318f59bc40

More syntax tests

view details

push time in 16 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 2aa19231bdda03aac96343f5b61503b147633b52

Add tests

view details

Austin Wright

commit sha 529ff4e94fd00a9a9254a543999ceb511cd47204

Tests for numbers and strings

view details

push time in 16 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha e69a47378edd613375841f12f0e092db3829103a

Allow parseInfo(text, schema) form

view details

push time in 16 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 28e4d29af323fcbdfdffb7f2b8dc64f22f6afb44

Split apart tests by function

view details

Austin Wright

commit sha fe2fbbe58030a8df5521ddaf2d976679f285a0e1

Add Stryker for testing

view details

push time in 16 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha 3951edc328768f64616593f947a14b6b229306e0

Test for expected module interface in interface.test.js

view details

push time in 17 days

push eventawwright/jsonschemaparse

Austin Wright

commit sha fe6dbdf161721c9b7bdb5974b13071e4dfdb6fc9

Add support for unevaluatedProperties There has to be something wrong here, all the tests pass with only a few lines of code

view details

push time in 17 days

issue commenttdegrunt/jsonschema

Plans to support latest JSON Schema 2019-09 version?

@chaeron Good question... It's one of the next things I'm working on. If you have a specific feature you're looking for, thumb up or drop a comment in an issue, or file a new issue if necessary, and I can look at that first.

chaeron

comment created time in 21 days

issue closedtdegrunt/jsonschema

Verifying that an object does _not_ have a certain property?

I wasn't able to find anything in the docs about this, is it possible? or is there a better way to think about this?

I was thinking something like:

let schema = {
  "id": "/test",
  "type": "object",
  "restrictedProperties": [
    "cantHaveThis",
    "orThis"
  ]
}

Main issue I'm trying to extra double check is accidental nesting

making sure:

{
  test: {
    props: {}
  }
}

isn't accidentally:

{
  test: {
    test: {
      props: {}
    }
  }
}

Thanks in advance

closed time in 21 days

dadambickford

issue commenttdegrunt/jsonschema

Verifying that an object does _not_ have a certain property?

You can also do something like:

{
"properties": {
   "cantHaveThis": false,
   "orThis": false
}
}
dadambickford

comment created time in 21 days

issue closedtdegrunt/jsonschema

Plans to support latest JSON Schema 2019-09 version?

Do you have any plans to support the latest JSON Schema 2019-09 version?

closed time in 21 days

chaeron

issue commenttdegrunt/jsonschema

Plans to support latest JSON Schema 2019-09 version?

@chaeron Yes!

chaeron

comment created time in 21 days

pull request commentjson-schema-org/json-schema-spec

Reference ECMAScript 5.1 specifically (#821)

@ssilverman Good suggestion @Relequestual I also added a # to your PR description to make it a link

Relequestual

comment created time in 21 days

issue commentOAI/OpenAPI-Specification

Define formal media type (MIME type) for Swagger Object

Ok, I gather that it's entirely possible to use a JSON Schema to define profiles of an application/json document. It might be the case a JSON Schema isn't necessarily a profile, but it can certainly be the case.

Before we get too far off topic, I think the question becomes, can we use profiles to distinguish version? If a profile is required to correctly interpret an OpenAPI media type, we don't gain anything over just using application/json with a profile.

philipashlock

comment created time in 24 days

issue commentOAI/OpenAPI-Specification

Define formal media type (MIME type) for Swagger Object

HTML is not a profile of SGML/XML

Besides the fact HTML is a separate media type, is there any reason this should be the case? An XML processor can read an application/xhtml+xml document without any knowledge of what HTML is. It can even perform some simple changes, like collapsing whitespace, or refactoring namespace declarations.

It seems the issue is XML semantics are so generic, there's not much else you can do with it.

But suppose I know the XML document is HTML, then there's more I can do with it.

And suppose I know the HTML document is hCard, or RDFa. Then there's even more I can do with it. Being able to express this seems to be the primary benefit of profiles.

think along the lines of HTML (a schema) and the good old STRICT and LOOSE profiles of it (two ways to constrain the HTML schema).

So you consider a DTD to be a kind of profile? Isn't a DTD a kind of schema?

philipashlock

comment created time in 24 days

push eventfullstackwiki/fullstackwiki

Austin Wright

commit sha 38c199ce2b4c926c77e8d7dab43ec186de95e57e

E-Mail address: describe line length limits

view details

push time in 25 days

push eventfullstackwiki/fullstackwiki

Austin Wright

commit sha 5f17e303acaf6e64dae889c53d86e4df0d69321f

Add section on internationalized addresses

view details

push time in a month

issue commenthttpwg/http-core

Variants cause conflicts in browser cache

Isn't this bug report for browser vendors?

namedgraph

comment created time in a month

issue commentOAI/OpenAPI-Specification

Define formal media type (MIME type) for Swagger Object

@dret I'm sorry that this keeps coming up, I think it's more that we're looking for consensus from the broader community, and I saw you disagree that a schema can be a profile, but I don't understand why. I would like to understand why, though.

I'm not sure about OpenAPI, but at least as far as JSON Schema defines it, a schema seems like a kind of profile:

a profile can be described as additional semantics that can be used to process a resource representation, such as constraints, conventions, extensions, or any other aspects that do not alter the basic media type semantics.

✅ JSON Schema adds constraints to documents, and allows additional information to be read out of a JSON document; but it does not alter the JSON semantics.

A profile MUST NOT change the semantics of the resource representation when processed without profile knowledge, so that clients both with and without knowledge of a profiled resource can safely use the same representation.

✅ e.g. an intermediate HTTP node (that does not understand profiles or JSON Schema) could add or remove whitespace without affecting a JSON Schema aware processor.

Profiles can be combined, meaning that a single resource representation can conform to zero or any number of profiles.

✅ Multiple JSON Schema documents may be applied, forming a logical intersection

Profiles are identified by URI.

✅ JSON Schemas are identified by URI

However ... the URI in this case only serves as an identifier

✅ JSON Schemas are not (necessarily) available over the network, and most applications expected to work without ever dereferencing a profile URI (unlike a DTD).

Thus, clients SHOULD treat profile URIs as identifiers and not as links, but profiles MAY be defined in a way that the URIs do identify retrievable profile description and thus can be accessed by clients by dereferencing the profile URI.

✅ JSON Schema does permit this, but downloadable representations are retrieved by following the "describedBy" link relation.

For profiles intended for use in environments where clients may encounter unknown profile URIs, profile maintainers SHOULD consider to make the profile URI dereferencable and provide useful documentation at that URI.

✅ We suggest doing this for the benefit of human debugging

If any of this doesn't seem correct, I'm very curious to hear your take, @dret.

@larsgsvensson wrote:

If the profile URI would point to a set of documents

I think this is the only issue here, if you mean something that can be downloaded, then another link relation would be appropriate.

philipashlock

comment created time in a month

push eventfullstackwiki/fullstackwiki

Austin Wright

commit sha e5914cf2f4bd9b40b74a8aa4b4c95fcc51f83d72

Add Web and E-Mail sections

view details

push time in a month

push eventawwright/uri-template-router

Austin Wright

commit sha df82f5decd914994f3e9cbddb38910ab7cf7d21d

Add gh-pages publishing script

view details

Austin Wright

commit sha 7711241f3b7de4419b9dffb0200a6104e4c82b91

Add Router#resolveRequestURI function

view details

push time in a month

issue closedtdegrunt/jsonschema

Typed array validation containing undefined values succeeds

> js = require("jsonschema")
{ Validator: [Function: Validator],
  ValidatorResult: [Function: ValidatorResult],
  ValidationError: [Function: ValidationError],
  SchemaError: [Function: SchemaError],
  validate: [Function] }
> js.validate([1, undefined, 3], {type:"array", items:{type:"integer"}}).errors
[]

No errors. It seems the lib treats undefined as a possible integer, which is strange and highly surprising to me. It sounds like a bug, but I'm not sure if the JSON schema spec would just allow that.

FWIW, jsonvalidator.net raises a validation error with this example:

It may be because undefined doesn't exist in JSON land, as serialization will always convert them to null, which pass validation. It's up to you to decide if you want to support js values (here undefined) along JSON ones (but in any case users should be explicitly warned about it in the docs).

closed time in a month

n1k0

issue commenttdegrunt/jsonschema

Typed array validation containing undefined values succeeds

This seems to be a duplicate of #211, if you have any further questions feel free to comment there, or open a new issue.

n1k0

comment created time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 7f63043d3c21c5b515b67efc5fe5f6d0ae20abf0

Update website

view details

Austin Wright

commit sha 0a484ce97737663568028cb11c996c5844f50fd1

gh-pages build

view details

push time in a month

create barnchawwright/jsonschemaparse

branch : gh-pages-makefile

created branch time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha c6d75b53bcf692f62ed6cd43df900c728057993e

Move Schema/SchemaRegistry tests to separate file

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 0e82f7c92f18757d87898c02ef08d0a25f416055

Move Schema/SchemaRegistry tests to separate file

view details

push time in a month

created tagawwright/jsonschemaparse

tagv0.0.9

Streaming parser for JSON with automatic validation and customizable parsing

created time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 95dd4351e6f74083741e5534958c7e5a5a9f5f6c

Ignore website build products

view details

push time in a month

PullRequestReviewEvent
PullRequestReviewEvent

push eventawwright/jsonschemaparse

Austin Wright

commit sha 9443fbfb2c4c086a1653fffa398e34f1d96cca89

docs: Lint the schema too

view details

Austin Wright

commit sha 27f5bac93ea94c3f4018376cfc04c7b946e2e6de

gh-pages build

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 9443fbfb2c4c086a1653fffa398e34f1d96cca89

docs: Lint the schema too

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 79f3fcdb5816dd6457f8fda6b627c2e36942db47

docs: Add streaming example

view details

Austin Wright

commit sha d2c523c88696dae93dbf07775e9e837d4dcbec9a

gh-pages build

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 79f3fcdb5816dd6457f8fda6b627c2e36942db47

docs: Add streaming example

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 35da8409465c658d75785b81a6d3904c0e27f9ad

docs: Typos

view details

Austin Wright

commit sha e9b91098e2bff55741dc2fdc3c1a55c742dc5a58

gh-pages build

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 35da8409465c658d75785b81a6d3904c0e27f9ad

docs: Typos

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha c4c49a2f50aa6fd4b681f9ab2902b74ca20f3ad1

Update dark mode colors

view details

Austin Wright

commit sha cf07cf26dcf48a939a0243b33b6e0bf1bd11a925

gh-pages build

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha c4c49a2f50aa6fd4b681f9ab2902b74ca20f3ad1

Update dark mode colors

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 809cba2787e72307d7f55ad2ee37edcd0c6aed86

Fix website build

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 809cba2787e72307d7f55ad2ee37edcd0c6aed86

Fix website build

view details

Austin Wright

commit sha dcbcc96b48c612e5230a395bfba704bd330658e1

gh-pages build

view details

push time in a month

push eventawwright/jsonschemaparse

Austin Wright

commit sha 5e99db5b84ff0e3cb4594df40d2ded01d633d970

Fix website build

view details

Austin Wright

commit sha 58693637d16d9d04db8d7bd85ba2da8bebf56d22

gh-pages build

view details

push time in a month

pull request commentjson-schema-org/json-schema-spec

Clarify how JSON Schema works with a superset of the defined data model

I took the paragraphs out and the behavior of validation keywords remains undefined.

awwright

comment created time in a month

push eventawwright/json-schema-spec

Austin Wright

commit sha 8afae0499951ce55266b7e7fee57e859410ec362

Clarify how JSON Schema works with a superset of the defined data model

view details

push time in a month

created tagawwright/json-schema-spec

tag970a

The JSON Schema RFC sources

created time in a month

more