json-schema-org / json-schema-org/website

Add typify in JSON Schema Ecosystem

Open
#1,855 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

dependencies needs-info Status: Triage
Dominant language
HTML
Stars
169
Forks
484
Avg merge
2d 2h
Merged PRs (30d)
6

Description

Tool Name

typify

Tool Description

I have nothing to do with it, but typify should probably be added, as it seems to more active than the other schema-to-code tools for Rust.

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
  • linter
  • linter-plugins
Languages

Rust

Environments

CLI

Dependencies on Validators

No response

Creators

Oxide Computer Company

Maintainers

@oxidecomputer

License

Apache 2.0

Source Repository URL

https://github.com/oxidecomputer/typify

Homepage URL

https://crates.io/crates/typify

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

No response

Bowtie Compliance Testing

No response

Tooling Listing Notes

No response

Compliance

No response

Landscape Information

No response

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.

Research direction

Start by inspecting the website's existing ecosystem tool listings and how entries are represented. Add typify using the supplied repository, homepage, Rust, CLI, schema-to-code, Apache 2.0, and draft-7 details; done means the tool appears consistently in the listing with its metadata.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
documentation
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.