Priyatam Mudi

I would be happy to review your PR in Garden for including `@supports` query.

A PR is nice to have :). In general, I would be interested in ideas focused on improving core CSS standards compatibility, versus utilities.

I won't use it, but I agree with @xcthulhu that we should have better error reporting if something is obviously incorrect—which is a larger issue, I think.

I'll take care of this soon.

@noprompt @jeluard [postcsss](https://github.com/postcss/postcss) community created many plugins based on these new extensions and our ability to write these from garden as Types, combined with data structures would open to new...

I have the same issue, where refreshing a page renders a 404. @markkemper1 passing history.state in page.start still returns 404. @shuvalov-anton: how do you propose to handle page refreshes with...

Yes, I'm passing scalars, like so, and still get an error: ``` (let [gen (gen/generator schema {:scalars {:Datetime (local-date-time)}})] (g/sample (gen :LenderReferral) 1)) > Resolver specified in schema not provided....

I removed `:mutations :input-objects :enums` from the raw schema, and yet get this error: ``` Assert failed: Second arg to fmap must be a generator (generator? gen) generators.cljc: 100 clojure.test.check.generators$fmap/invokeStatic...

Sure, I'll provide this soon ...

Thanks @rwilson. I don't need an aws elastic load balancer client now (happy with the default one shipped with splyglass), and is running fine in production for seven months. The...