functions documentation

[NamanChhabra]

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [ ] I have signed the Adobe Open Source CLA.
• [ ] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[cfjedimaster]

I'd maybe show $join instead: https://docs.jsonata.org/string-functions#join

[NamanChhabra]

https://docs.jsonata.org/string-functions#join

this will be the case when we have array as the value of a key in json and the user wants to print that value as array itself. Also , there are some functions that have an output type of array so to print them we can use the $string() function.

[cfjedimaster]

I guess I can see that as something a person would do, but most humans don't 'read' arrays like that, and the consumers of the PDFs are probably more non-technical folks. I'm not saying this isn't a bad tip per se, but it just feels odd for us to show a random tip like this. I do think our docs could use a page with DocGen tips and tricks.