Graham Cox

One option is to do like react-query does and make it optional and disabled by default. But I fully understand the reticence to implement an experimental API 🙂

Example use case. System A depends on configuration data that's stored in System B. This configuration data is absolutely cacheable and doesn't change often, but when it does change then...

> Hello @sazzer , I don't think adding annotations is related with PactumJS. May be Github Actions pick the last failure reported. Adding annotations is nothing to do with PactumJS....

This is the result of only having a single Builder style test: https://github.com/sazzer/vitest-gha/actions/runs/10887364402 Conversely, this is the result of only having a single BDD style test: https://github.com/sazzer/vitest-gha/actions/runs/10887376975 If you compare...

I've just come across `derive_unsafe`, though that still fails. This code: ```rust #[nutype::nutype( sanitize(trim), derive(Clone, Debug, PartialEq, FromStr, AsRef), derive_unsafe(garde::Validate) )] pub struct UserID(#[garde(length(min = 1))] String); ``` Gives this...

So what's the best way to address this? Do I submit a proposal somewhere? Or do I just submit a PR? Or is there some other way? Cheers

This test fals: ``` #[test] fn test() { let value = json!({ "a": 1, "b": [ 1, 2 ] }); assert_json_snapshot!(value, @r###" { "b": [1, 2], "a": 1 } "###);...

For me personally - and I'm aware that there are so many more users to consider! - the most user friendly would be to keep using `assert_json_snapshot!()` but have it...

That's fair. My use case is API testing. I'm making HTTP calls to an API, deserializing the response into a `serde_json::Value` and then using Insta to compare that to the...

> > deserializing the response into a `serde_json::Value` and then using Insta to compare that to the expected value > > but doesn't `assert_json_snapshot` work with a `serde_json::Value`? Can you...