Comment 0 for bug 1364507
Revision history for this message
| Miguel Grinberg (miguelgrinberg) wrote | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
When validating a template, the heat API returns the "NoEcho" property of template parameters as a string, with values "true" or "false".
But for a client it is odd to have to check this property as a string, and is also error prone, since most people will assume this property comes as a boolean. This happened to me when I was implementing this property on Horizon. I did not realize there were quotes around "true" and "false" in JSON strings until I went with a debugger to inspect why my comparisons were not working right.
Would there be opposition if the API is changed to a return proper JSON boolean for this property? Horizon currently does not use this property at all, so no problems there. I guess the only risk is with other clients, if there are any.