Add rock_solid in JSON Schema Ecosystem

Open Beginner friendly
#2,430 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
elixir, erlang
Domain
documentation

Research direction

No repository file or test is named in the issue. Start by locating the website's existing JSON Schema Ecosystem tool listings, then add rock_solid using the supplied description, repository, homepage, language, license, supported dialects, and compliance notes. Done means the tool appears accurately in the ecosystem listing.

Written by the indexing model from the issue text.

Description

dependencies Status: Triage
Tool Name

rock_solid

Tool Description

Elixir library to generate test data from JSON schema

Action Type
  • Add Tool
  • Modify Tool
Tooling Types
  • validator
  • hyper-schema
  • benchmarks
  • documentation
  • LDO-utility
  • code-to-schema
  • data-to-schema
  • model-to-schema
  • schema-to-types
  • schema-to-code
  • schema-to-web-UI
  • schema-to-data
  • util-general-processing
  • util-schema-to-schema
  • util-draft-migration
  • util-format-conversion
  • util-testing
  • editor
  • editor-plugins
  • schema-repository
  • registry
  • linter
  • linter-plugins
Languages

Elixir, Erlang

Environments

Any platform that supports Elixir.

Dependencies on Validators

https://github.com/lud/jsv

Creators

Ignacio Goldchluk (@IgnacioGoldchluk)

Maintainers

Ignacio Goldchluk (@IgnacioGoldchluk)

License

MIT

Source Repository URL

https://github.com/IgnacioGoldchluk/rock_solid

Homepage URL

https://hex.pm/packages/rock_solid

Supported Dialects
  • 1
  • 2
  • 3
  • 4
  • 6
  • 7
  • 2019-09
  • 2020-12
Additional Dialects

No response

Bowtie Compliance Testing

No response

Tooling Listing Notes

Supports draft-04 to 2020-12 and can generate data for recursive schemas, schemas with dependentSchemas, if/then/else, references to remote schemas, etc.

Compliance

Some keywords are not supported due to their dynamic nature ($dynamicAnchor, unevaluatedProperties, etc.) and a long chain of if/then/else and/or dependentSchemas can cause a branch explosion and crash the library.

Landscape Information

No response

Dominant language
HTML
Stars
169
Forks
484
Avg merge
7h 58m
Merged PRs (30d)
6

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from json-schema-org/website

All issues in json-schema-org/website

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.