BIND 10 #3239: Configuring int value in quotes print funny error

[BIND 10 Development]

#3239: Configuring int value in quotes print funny error
-------------------------------------+-------------------------------------
            Reporter:  tomek         |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  low           |                       Status:
           Component:                |  reviewing
  configuration                      |                    Milestone:
            Keywords:                |  Sprint-20131015
           Sensitive:  0             |                   Resolution:
         Sub-Project:  Core          |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => UnAssigned
 * status:  assigned => reviewing


Comment:

 Replying to [comment:8 muks]:
 > Also, re-reading the error message printed:
 > {{{
 >  Error! 600 is not an integer
 > }}}
 >
 > it would be nice to either (1) show the quoted value as-is (with quotes)
 or (2) print the parsed typename of the value (vs. expected typename).
 This would aid the user in understanding it more clearly. The message "600
 is not an integer" looks like it guessed it as an integer and is saying
 it's not an integer.

 Option (2) has also been implemented in the `trac3239_3` branch.

 Note that no tests have been adjusted for this work as just the error
 message has been changed.

 Suggested `ChangeLog` entry:
 {{{
 XYZ.    [func]          muks
         When displaying messages about mismatched configuration data types
         in entered values (between the supplied value type and expected
         schema type), bindctl now includes both the supplied and expected
         configuration data types in the returned error. The user has more
         information on what caused the error now.
         (Trac #3239, git ...)
 }}}

 Up for review.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3239#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development