| Age | Commit message (Collapse) | Author |
|---|
|
Previously, bool2str() accepted a broad array of boolean values and
bare strings, without any attempt to validate that the strings in any
way resembled "true" or "false" (or any of the other values bool2num()
accepts). This commit narrows the input confinement to TrueClass and
FalseClass, which means that bool2str() will only interpolate
strict boolean values now.
|
|
|
|
Python likes to have its constants Capitalized, and the capitalize
function only understands strings... so I shave a yak.
bool2str will convert a boolean to its equivalent string value,
and camelcase extends on uppercase & downcase to convert an underscore
delimited string into a camelcased string.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Numerous changes to update testing gems.
|
|
It turns out that in 3.x the refresh functionality doesn't actually
exist yet, so testing it makes no sense.
|
|
Add beaker framework.
|
|
This prepares the module for beaker acceptance tests.
|
|
PUP-1724 Don't modify the paramaters to deep_merge
|
|
hash example has misplaced comas
|
|
|
|
Make sure location_for is used when installing Puppet.
|
|
|
|
Readd location_for
|
|
location_for is used in Jenkins to transform a passed in git
repo into something usable by bundler.
|
|
|
|
This work updates a number of Gems to the latest versions (rspec,
rspec-puppet), and updates and tweaks a bunch of tests to work
with the updated gems.
|
|
[WIP] Spec overhaul.
|
|
This work updates a number of Gems to the latest versions (rspec,
rspec-puppet), and updates and tweaks a bunch of tests to work
with the updated gems.
|
|
Patch metadata
|
|
|
|
Supported Release 3.2.1
|
|
Summary
This is a supported release
Bugfixes
- Fixed `is_integer`/`is_float`/`is_numeric` for checking the value of
arithmatic expressions.
Known bugs
* No known bugs
|
|
[don't merge] Prepare for supported modules.
|
|
|
|
|
|
Instead of modifying the first paramater of deep_merge due to the
use of the merge! function, instead use merge to return a copy of
the merged object. This allows one to continue to use the original
first parameter after the call to deep_merge.
|
|
(DOCUMENT-21) add docs for file_line to README.markdown
|
|
Fix strftime documentation in README
|
|
Markdown was barfing due to typo
|
|
Remove trailing whitespace
|
|
|
|
* DavidS-broaden-pick-arguments2:
(PUP-638) Add a pick_default() function that always returns a value.
(PUP-636) Ignore generated file
|
|
This version of pick() does not error out, instead always returning at least
the last argument, even if that too has no "real" value.
|
|
|
|
(PUP-1459) Add support for root_home on OS X 10.9
|
|
Without this, you have to look at the source file
(lib/puppet/type/file_line.rb) to know what it does. This adds that
documentation.
|
|
The documentation contained references to future decisions about
functionality.
Text rephrased for clarity.
|
|
I expect a function called "is_numeric" or "is_integer" to check if a
variable is an integer or a number even if the variable passed by isn't
a string nor a number at all. Otherwise we should call them
is_string_a_number and is_string_an_integer and we have then to remove
the check for .is_a?(Number) and .is_a?(FixNum)
now checking also if it is a hex or octal number
improved/corrected checking for integer
* checking against Integer instead of Fixnum so that
also Bignum is matching
* now .is_a? Integer is done first so this is quiet fast
Now many types of numerics are recognized.
1. Float/Integer values (signed or unsigned, with exponent or without)
2. octal and hex check
3. except hex numbers and the "0." in a float lower than 1 can be prefixed
with a '0'.
whitespaces shouldn't be allowed as prefix/suffix
string representation of numbers should not contain any type of
whitespace.. the user is responsible to clean a string before checking
it..
fix documentation and added more checks
tried to be 99.9% backward compatible
* for now the decission is post poned if hex and octal numbers
should be allowed or not (is_numeric)
* native Bignum is now also a valid integer class
fix problem with old 1.8 ruby and Hash.to_s/Array.to_s
In ruby < 1.9 array and hashes would be recognized as numeric
if they have a special format:
1.8:
[1,2,3,4].to_s = "1234"
{1=>2}.to_s = "12"
1.9:
[1,2,3,4].to_s = "[1, 2, 3, 4]"
{1=>2}.to_s = "{1=>2}"
|
|
Enable fast finish in Travis
|
|
http://blog.travis-ci.com/2013-11-27-fast-finishing-builds/
|
|
getent does not exist on 10.9 so this commit uses
dscacheutil to query the homedir for the root user.
|
|
This closes GH-201.
|
