What version of ACF introduced the includeEmptyFields argument to listToArray(). Where should I have looked for that info?

First port of call ought to always be the docs, but Adobe are a bit rubbish at keeping them up to date (as is the case here @Mark Takata (Adobe) / @saghosh... no mention of when

includeEmptyFields

was added on https://helpx.adobe.com/coldfusion/cfml-reference/coldfusion-functions/functions-l/listtoarray.html 😐). Failing that google "what's new in coldfusion [version]" and there'll be a page with links to the new features in that version... one needs to hunt backwards through versions to try to find the change. Or get onto trycf and write some code using the "new" feature, and step backwards through the versions until the code breaks. It seriously shouldn't require all this bullshit, Mark.

Thanks @Adam Cameron.

Take docs away from Adobe. Adobe and community all support cfdocs.org. There I said it. Gets old seeing so many call outs to Adobe and Mark lol. Energy focused towards actual change is cool. Until then, sorry Mark.

All good. CFDocs exists and is great. And while no one seems to have noticed or cares, the way docs looked around 1 year and 8 months ago vs now is like night and day. We've updated many hundreds of pages, mostly based on user input as well as internal finds. It isn't sexy, it isn't "exciting", but it is a testament to Saurav and his team's hard work. And how much of an annoyance I can be lol. We will keep working on improving the docs. And some people will always crap on them, no matter how hard or long we work. That's just the way. Some people will never be happy about anything, ever. I listen to their useful advice and ignore the abuse. And I very much appreciate all the rest of the community who provide feedback & help to other without being jerks about it.

includeEmptyFields

was present in CF9

The docs say that CF9 added the multiCharacterDelimiter. Which implies that includeEmptyFields was already there... So now we're talking CF8 at the latest. maybe it's always been there?

me goes searching for the Allaire CF2 manual... I know it's here somewhere, next to the Ark of the Covenant...

You can "subtweet" me all you like @Mark Takata (Adobe), but ppl pay $1000s for CF and I do not think it's an unreasonable baseline expectation that the docs are kept up to date without ppl chasing you to do it. I mean even with the updates that get done, there's the perennial tendency to do the absolute minimum required to get a box ticked, eg: we mention one thing missing from the history of a function. That gets fixed. Cool (and thanks). But is there any effort to review all the other ones? No. Just that one. To make the current squeaky wheel go away. As for whether or not stuff gets updated, and how (literally) thankless it is... this is perhaps because I don't recall ever seeing @saghosh come back after some tweak gets done to fix something that's been raised saying "yeah thanks we've fixed that. Wanna go have a look to see if we've nailed it properly?" You know, like would normally happen with bugs / fixes. They are doing work - good, and again: thanks - but the approach lacks the polish it could have, and the reality is it's all reactive and work that should have already been done in the first place. Without it causing your dev community grief.

k.

Thank you so much Adam for your feedback. Thanks for all the work and help on the docs over the years. As far as the changes are concerned, its best if you could drop an email to saghosh@adobe.com or raise a JIRA ticket. Again many thanks and apologies on the communication gap.

@saghosh Jira ticket? There's a Jira project for CF docs?

No, you can use the usual method of creating a ticket. while creating the ticket, select Component as Documentation.

Gotcha, cheers pal.