ok. Thanks.
Best,
André
Am 07.05.2007 um 16:13 schrieb Mike Schrag:
> In the meantime, I added it to the list of "NS Collections", since
> it sort of has that same semantic ... This means you can now
> control it by turning off "warn if missing key on NSDictionary/
> NSArray (which is already mislabeled, but NSSet is included too).
> It should probably be something like "warn if missing key on
> classes that commonly have dynamic keys".
>
> ms
>
> On May 7, 2007, at 10:04 AM, André Koppany wrote:
>
>> mmh.
>>
>> I think I have to look for option 4 and pray that "magic mike"
>> would build in that keypath regex validation thing.
>> With option 1 or 2 I loose to much of the power of the tools.
>> Option 3 is not usable because we are working mainly with
>> localized apps which have a minimum of 20 bindings for loc. in the
>> components.
>>
>> Best,
>> André
>>
>> Am 07.05.2007 um 15:51 schrieb Mike Schrag:
>>
>>>> "There is no Key 'firstName' for the keypath 'loc' in CBla...."
>>> Oh.. right .. wait a minute. Yeah it's finding "loc" just fine,
>>> it just has no ability to validate that keypath. You have really
>>> just a couple options right now:
>>>
>>> 1) switch from "error if missing key on NSKeyValueCoding" to
>>> "warn if missing key on NSKeyValueCoding", but you'll still get
>>> warnings
>>> 2) turn off both, but then you'll get what Anjo was talking about
>>> (where you lose a lot of potential errors/warnings)
>>> 3) add // VALID onto the end of the line that is having the
>>> problem (which tells the validator to just ignore problems on
>>> that line)
>>> 4) wait for me to add support for something like custom keypath
>>> regex validations, or however it ends up -- not sure when that
>>> will be right now
>>>
>>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Mon May 07 2007 - 10:36:58 EDT