Skip to content
Snippets Groups Projects
Select Git revision
  • iopsys
  • develop
  • master default protected
  • gh-pages
  • 0.4.x
  • v0.5.0-rc23
  • v0.5.0-rc22
  • v0.5.0-rc21
  • v0.5.0-rc20
  • v0.5.0-rc19
  • v0.5.0-rc18
  • v0.5.0-rc17
  • 0.5.0-rc16
  • v0.5.0-rc15
  • v0.4.7
  • v0.5.0-rc12
  • v0.5.0-rc11
  • v0.4.3
  • v0.5.0-rc10
  • v0.5.0-rc9
  • v0.5.0-rc8
  • v0.5.0-rc7
  • v0.5.0-rc6
  • v0.5.0-rc5
  • v0.5.0-rc4
25 results
Compare
user avatar
[WIP] RC16 for v0.5.x (#464)
Alvaro Cabrera Durán authored 
* Lock deps

* Run npm audit fix

* Remove old deps; cleanup

* Fix package; remove types from sources

* Delete old typescript sources; cleanup

* Move to modern testing and libs; cleanup

* Remove ancient build scripts and lib; cleanup

* Upgrade ESLint rules

* Fixed schema tests; cleanup

* Fixed scripts for CI

* Watch more extensions; cleanup

* Apply changes from PR #432

* Fix #458

* Add test for #455

* Make ESLint happier; take 1

* Make ESLint happier; take 2

* Add is-my-json-valid to validators

* Use Object.assign() instead; fix

* Add tests for #456; cleanup

* Add ajv to validators; remove jayschema

* Fix #453; handle single-prop cases

* Add fixedProbabilities option to handle random vs fixed cases; fix #443

* Add tests for #446; cleanup

* Ignore properties.default; fix #442

* Add tests for #425; fixed

* Add tests for #427; fixed

* Fill up with patternProperties; fix #416

* Add support for built-in templates; fix #419

* Add tests for #408; wont fix

* Merge references into schemas; fix #345

* Fill missing properties with required ones; fix #369

* Support for seeding on tests; add #379 tests

* Improve enum support for other types; fix #405

* Query and pick for random items; fix #400 #429

* Enable resolveJsonPath by default; fix #407

* Add methods for clearing out containers; fix #440

* Remove deref from dependencies; fixing refs issues

* Fix resolve order; await on tests

* Cleanup

* Add tests for #386; pending

* Add deprecation logs; cleanup

* Exclude external deps to get ~27KB dist, bundle is ~413KB; fix

* Call .resolve() on tests; fix

* Fix built filenames; cleanup

* Revert "Enable resolveJsonPath by default; fix #407"

This reverts commit 48b67ab027bc5379efd4da1554be6af40725eeb5.

* Fix exported name as JSONSchemaFaker

* Add missing useExamplesValue() from #441; fix

* 0.5.0-rc16

* Fix tests on CI

* Use Object.assign() instead; fix

* Make tests run without async/await; fix

* Apply fixedProbabilities on arrays; fix #456

* Increase timeout on CI

* Not used anymore

* Cleanup; WIP

* Moving and updating docs; WIP

* Improve docs

* Enable ignoreMissingRefs flag support; fix

* Typo

* Force typecasted type fo fix #467

* Fix bullets

* Build dist files

* Fixed tests

* Test for custom typecasting; fix

* Run all tests; fix
57331700
History
user avatar 57331700
History
Name Last commit Last update
.github
dist
docs
logo
src
tests
.editorconfig
.eslintrc
.gitattributes
.gitignore
.npmignore
.travis.yml
CHANGELOG
CONTRIBUTORS
LICENSE
README.md
package-lock.json
package.json
README.md

JSON Schema Faker logo

Donate Build Status NPM version Bower version Coverage Status

Gitter Dependency Status devDependency Status

Inline docs Typedoc

Use JSON Schema along with fake generators to provide consistent and meaningful fake data for your system.

What's next?

The latest RC16 comes with some deprecations and breaking-changes towards v0.5.x API:

  • deprecated — You will not longer be able to call jsf() and get a fully-dereferenced result. It will just generate given refs and inline ones, nothing else.
    • jsf.generate() is the sync-version, with partial dereferencing through given refs, etc.
    • jsf.resolve() is the async-version, with full dereferencing, given refs are also supported.
  • deprecated — TypeScript sources are not longer used, however d.ts definitions will be updated on time.

Review here: https://github.com/json-schema-faker/json-schema-faker/pull/464

Most documentation from README.md was moved to docs/ and it should have its own place there, on the website, or wiki pages, etc. This part is unclear yet, so any suggestion is welcome on the PR above.

Contributors

We are more than happy to welcome new contributors, our project is still being developed, but we need more feedback!

Please see our contribution guide to learn how.

We are looking for your help!

We have a gitter room for this project, if you want contribute, talk about specific issues from the library, or you need help on json-schema topics just reach us!

Have some ♥️ for JSON-Schema-Faker? You can support the project via:

Take a look at the technical documentation page.