[chef-dev] Re: Re: Re: How to represent nested attributes

[Joseph Anthony Pasquale Holsten < >]

A deprecation notice in the client code is certainly reasonable.

On Jul 7, 2014, at 2:40 PM, Noah Kantrowitz 
<
 >
 wrote:

> Maybe before 11.14 is finalized, we should change the whitelist code to use 
> .s then? Not sure if thats too big a change for an RC :-/
> 
> --Noah
> 
> On Jul 7, 2014, at 2:37 PM, Adam Jacob 
> <
 >
>  wrote:
> 
>> I lean towards dots as well. Sadly, dots in the search syntax probably 
>> won't be forthcoming, and underscores are a terrible separator. 
>> 
>> 
>> On Mon, Jul 7, 2014 at 2:31 PM, Joseph Anthony Pasquale Holsten 
>> <
 >
>>  wrote:
>> My tooling takes attribute selectors with `.` separators and drills into 
>> things accordingly. Because JSON.
>> 
>> eg 
>> https://github.com/josephholsten/discoteq/blob/master/chef/service.go#L128
>> 
>> On Jul 7, 2014, at 2:09 PM, Noah Kantrowitz 
>> <
 >
>>  wrote:
>> 
>>> Something that could maybe do with a bit of standardization. The issue is 
>>> given some nested hashes, how do you indicate a specific key. The 
>>> attribute declaration and the new attribute whitelists use a "/" 
>>> separator, most knife command line options use a "." and partial searches 
>>> use none and require a real array. Thoughts?
>>> 
>>> --Noah
>>> 
>> 
>> 
>