Empty module generated when no `title`

[spencerwilson]

Given the following input:

{
  "type": "array",
  "minItems": 1,
  "uniqueItems": true,
  "items": {
    "type": "string"
  }
}

cargo-typify 0.0.13 generates

#![allow(clippy::redundant_closure_call)]
#![allow(clippy::needless_lifetimes)]
#![allow(clippy::match_single_binding)]
#![allow(clippy::clone_on_copy)]

use serde::{Deserialize, Serialize};

I suppose it doesn't know what to call anything if title is missing. Maybe this should error?

[ahl]

Agreed that this is a lousy experience! How are you using typify? Is this from a build.rs or maybe cargo-typify?

[spencerwilson]

Via cargo-typify currently! I make a couple manual edits to the generated output (adding a module comment and an #![allow(dead_code)]), so can't easily build in a build.rs, AFAIK.

[jayvdb]

@spencerwilson , it is not too hard to slurp the generated output in using syn and then use syn to inject a few bits into the generated output before writing to disk.

To read into syn and then get it back out:

let file = syn::parse2::<syn::File>(typespace.to_stream())?;
// do File ops here
let new_contents = format!("{}", file.to_token_stream());

Or you could generate a string if the bits you want to add a simple enough - e.g. headers/footers.

[spencerwilson]

Ah thanks for the pointer, @jayvdb , I may try that 🙇

[RoastVeg]

Would it be possible for typify to substitute the name of the file as the title, if the title is unset in the schema itself?