8 Commits (32a78f50b05bc73c652a00ff550dd21bdd63315e)

Author	SHA1	Message	Date
Jens Ulferts	701f196c25	eager load user and version custom fields in wp representer	8 years ago
Jens Ulferts	a6d265eb79	force bool custom values to be stored uniformly	8 years ago
Alex Coles	57618b25ec	Replace dynamic finder usages with #find_by, etc. ... This patch replaces all dynamic finders, for the sake of consistency, although only some methods are deprecated. See: https://github.com/rails/activerecord-deprecated_finders#active-record-deprecated-finders * Revert some `User#find_by_login` usages in cuke steps accidentally removed in 74228b59. User Story # 20325 Signed-off-by: Alex Coles <alex@alexbcoles.com>	10 years ago
Jan Sandbrink	f9b242884d	let custom values accept their native type ... - add specs for strategies to parse their typed representation as valid (instead of only their stringly typed counterpart) - add specs to int and float strategy regarding accepting eachother - fix int custom values accepting float inputs (which would work, but omit the fractional part) - fix date custom values not accepting on Date	10 years ago
Jan Sandbrink	122384b8f2	use "be" instead of "eql"	10 years ago
Jan Sandbrink	05bdba6a29	fix preview of true custom field in form ... :typed_value would not return true if the internal value was set to true (it only ever expected it to be '1')	10 years ago
Jan Sandbrink	348d3c746e	fix submission of "false" as CF value ... it was not possible to set a custom field to false via APIv3. Apparently the way the value is set in other places does not involve "real" boolean types	10 years ago
Jan Sandbrink	25dec31c5a	extract some case statements into fancy strategies ... - 17 new files - lots of new lines of code - specs! - same functionality as before	10 years ago