oxidecomputer / oxidecomputer/typify
error or warn on non-json schema inputs
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 898
- Forks
- 114
- Avg merge
- 4h 18m
- Merged PRs (30d)
- 14
Description
I only get prelude output from cargo-typify with no types, from my .json
Maybe I am making a silly mistake.
xaa.json
I only get the .rs prelude output with no types on this file.
$ cargo typify -o /dev/stdout xaa.json
#![allow(clippy::redundant_closure_call)]
#![allow(clippy::needless_lifetimes)]
#![allow(clippy::match_single_binding)]
#![allow(clippy::clone_on_copy)]
use serde::{Deserialize, Serialize};
$
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running cargo typify -o /dev/stdout xaa.json with the attached xaa.json input and inspect how the CLI handles a schema that produces only the Rust prelude. Determine the expected diagnostic for this input, then verify that the command reports an error or warning instead of silently emitting no types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100