tracker issue : CF-4199894

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] ER for: isValid() datetimeobject

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/Fixed

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff ()

Created: 10/03/2017

Components: Language, Functions

Versions: 2016

Failure Type: Others

Found In Build/Fixed In Build: / 2018.0.0.309620

Priority/Frequency: Normal /

Locale/System: /

Vote Count: 0

This ER is for: isValid("datetimeobject")

With few exceptions (ex: cfqueryparam's cfsqltype and CGI variables), CF does not use underscores in attribute names, parameter values, variable names, etc.

Related Tickets: CF-3194042, CF-4179276 and CF-4179704.

Issue: CF2016 Update 3 introduced isValid("datetime_object", )  ..sigh

Since that was just added, it could be deprecated. And, honestly, isValid("social_security_number", ..) should be deprecated, b/c honestly who would type that instead of isValid("ssn", ..)?

BUT, *most importantly*, the following should be added: isValid("datetimeobject", ..)

Attachments:

Comments:

I debated logging this as "Bug" instead of "ER". The bug is that Adobe introduced another "underscore thing". And we keep having to log tickets to get those cleaned-out. Thanks!, -Aaron
Comment by Aaron N.
257 | October 03, 2017 06:48:05 AM GMT
Hi Adobe, Could you please change this from ER to Bug? Please see the following note on CF-4183487: Two Issues: 1) The request was for: isValid("datetimeobject", ..), not isValid("datetime_object", ..). For language consistency, underscores aren't used in new parameter/attribute names. Please read the full description of CF-4199894, including the ticket numbers mentioned in that ticket. 2) isValid("datetimeobject", now()) throws "Valid type arguments are: any, array, Boolean, date, numeric, query, string, struct, UUID, GUID, binary, integer, float, eurodate, time, creditcard, email, ssn, telephone, zipcode, url, regex, range , component, and variableName." That list doesn't include "datetimeobject", but should (it also doesn't include the erroneous "datetime_object"). Thanks!, -Aaron
Comment by Aaron N.
27269 | April 02, 2018 10:10:57 PM GMT