graphql-engine/v3/crates/opendds-derive/Cargo.toml

[package]
name = "opendds-derive"
version = "0.1.0"
edition = "2021"

[lib]
proc-macro = true
bench = false

[dependencies]
convert_case = "0.6.0"
darling = "0.13"
proc-macro2 = "1.0"
quote = "1.0"
syn = { version = "1.0", features = ["full"] }

[lints]
workspace = true
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2 2024-03-11 15:16:53 +03:00			`[package]`
			`name = "opendds-derive"`
			`version = "0.1.0"`
			`edition = "2021"`

Disable benchmarks in unit tests. (#376) This means that we can pass arguments to the Criterion benchmarks because the test binaries do not try and run. For example, if you run this: ``` cargo bench -- --warm-up-time=1 --measurement-time=1 ``` … it will currently fail, because it will also pass these arguments to the tests. Disabling the benchmarks for the tests fixes this. V3_GIT_ORIGIN_REV_ID: 10fe0683b82c506e1a11b24ca0a0a4041e37b655 2024-03-21 15:41:31 +03:00			`[lib]`
			`proc-macro = true`
			`bench = false`

Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2 2024-03-11 15:16:53 +03:00			`[dependencies]`
Remove unused dependencies using `cargo machete`. (#413) `cargo machete` is a very useful tool that figures out when you aren't using a dependency. I have run this locally to remove unused dependencies. I've also added a CI job to make sure we catch these in the future. Sometimes it reports false positives, e.g. when a dependency isn't used directly but in macro-generated code (e.g. with `strum`). I have added `"ignored"` clauses to the `Cargo.toml` files where appropriate. V3_GIT_ORIGIN_REV_ID: ed015089b695cec8eeb03ce455d6dd3cd312a016 2024-03-28 12:16:54 +03:00			`convert_case = "0.6.0"`
Custom deserializer for OpenDd objects (#313) V3_GIT_ORIGIN_REV_ID: 4c7a9380e517ac8e7ac1bd44dbe879918bd0d9a2 2024-03-11 15:16:53 +03:00			`darling = "0.13"`
			`proc-macro2 = "1.0"`
			`quote = "1.0"`
			`syn = { version = "1.0", features = ["full"] }`
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15 2024-04-08 13:13:26 +03:00
			`[lints]`
			`workspace = true`