Removing strict type-validation for string/int type configuration options (None is good!)

Hi all, Currently, one of the proof requirements within charm-tools is that all configuration options must have a default key with a matching type value for that key. Most notably, some charms omit the default key and use strict None/NULL checking within the charm. In order to statisfy this

Re: Removing strict type-validation for string/int type configuration options (None is good!)

Hi Marco, I have actually run in to this problem before you have my +1 for this! - Matt On Mon, Feb 10, 2014 at 8:49 AM, Marco Ceppi marco.ce...@canonical.comwrote: Hi all, Currently, one of the proof requirements within charm-tools is that all configuration options must have a default