ummm, <https://docs.lucee.org/reference/functions/...
# cfml-general
z
r
Thanks Zac, it's a reminder to check multiple documentation sources. It seems obvious to use Lucee docs if your using Lucee, but I tend to use cfdocs.org and saw it was OpenBD only https://cfdocs.org/structvaluearray. I won't make that mistake again:)
👍🏾 1
d
So its only ACF thats missing it. Dang, I'm so guilty of this. I use cfdocs.org 100%. I submitted a PR to cfdocs so that it mentions Lucee also supports this. https://github.com/foundeo/cfdocs/pull/1459
z
i always check both lucee docs and then jira, then if you confirmed it's missing, please file a bug. slack is a black hole
👍🏾 1
d
I'm realizing that more and more about Slack. Just now was my first time visiting lucee docs and I really like them.
z
the cross referencing is great for learning what's available
it's autogenerated from the actual tag and function definitions, always tracking the latest stable release, so currently 5.3.8.201
d
I have visited Jira before but its not in my muscle memory, neither is Adobe's bug tracker of ACF docs(specially because it sucks compared to other open source libraries I'm in to.)
z
our jira is also heavily cross referenced by labels so it's easy to jump around say image or zip bugs
d
Thanks Zackster. I'll definitely start to compare those sources next time.
z
i recently added links to test cases at the bottom of each page for lucee docs
d
How does work? I see the test case for structValueArray
whats the purpose of adding those test cases?
z
if you see any typos or something missing, you can just click the github icon to submit a PR
why does lucee have tests?
d
no, why include them as link in the docs? Like I know what tests are for but not sure what these CFCs are for?
z
I think of them as further, detailed examples, hence useful
d
oh
I see now. Oh geez this is very useful
z
😇
d
Dope. The issue tracker link is a good addition too.