Ted Driggs

This is now live as 0.20.0

Try `#[my_attribute(name = "name", sql_type(float = 3.5)]`

I think for that you'll need to do a custom implementation of `FromMeta`, or use the `#[darling(with = "...")]` attribute on the field in question to override the parsing function.

Sort of - you can create a private mirror of the enum that derives FromMeta and has a conversion into the public enum, and then have your custom impl of...

I don't think the way that `darling` handles absent fields would work for enum variants; that uses the `FromMeta::from_none` method on the field-type level, and we don't have a good...

I'd suggest trying this again, as a bunch of changes in enum variant handling just merged.

Attempting to repro this, I discovered something interesting. This errors: ```rust let _attr: syn::Attribute = syn::parse_quote!(#[type = false]); ``` But this doesn't: ```rust let _attr: syn::Attribute = syn::parse_quote!(#[hello(type = false)]);...

I've filed dtolnay/syn#1458 to request that `syn` handle this scenario without errors.

As noted in #1414 it seems that keyword identifiers are fine as long as they're inside the `List` portion; is there a way that `NestedMeta` could reimplement `Meta` parsing to...

The issue you're running into is what happens when the caller doesn't specify `path`. In that situation, `darling` will either use the function set in the field-level `#[darling(default = ...)]`,...