Branching from a previous post…
Here are a few ideas:
- I’m as guilty as the next guy, but I don’t know how we train developers to regularly review the documentation. Example: Just yesterday, a co-worker asked me if SnapLogic dates/times could be compared in expressions, so I gave my best educated answer and then thought to look it up and point them to the documentation Comparing Dates.
(this point may not be helpful, but provided as an example)
- All new or modified expression language methods/behaviors should be included in the platform release notes and/or an available change log. I’ve missed out on a lot of new e-lang additions which would have been beneficial to me much sooner. As well, it’s been a long while, but we’ve been impacted by one or two language syntax fixes that were working the way we were implementing and then failed after the release.
- Advanced tutorials/examples (i.e. YouTube) for Expression Language and Expression Library would be great. Our team doesn’t utilize the Expression Library feature near enough, but it’s an extremely useful feature. Also, the arrow functions (another beneficial feature) are a new concept for some inexperienced developers.
- UI / UX
- A “suggest” feature (with documentation) would be cool when writing expressions in a mapper or other snap. After I type out a string or an object representing a string, It would be handy to see all the string methods pop up in a suggest list (maybe after a pause and possibly provide a link to the string documentation).