PSA to anyone stumbling on to this thread.
I've confirmed a bug with support introduced somewhere in 8.1 that will break find and replace if you use the word "Arguments" in your doc string (triple speech marks).
Apparently this clashes with the inbuild Ignition function documentation and confuses the parser.
So avoid using that like i did, and stick to the shorter version of "Args"... 
Now to find all the places i've done it amongst hundreds of windows..
The good news is that it only affects Vision extension functions in particular. A bad choice when we first introduced their serialization that was basically unavoidable when extracting them back out again to upgrade, unfortunately.
Will it still be a problem if there is another def block inside the main extension function?
Like this for example?
No. Only a triple-double-quoted bare string, on the very first line, containing the literal string Arguments: will cause the issue. Break any of those conditions and you're fine.
Docstrings per Google style
It will be amazing if you clould add a context menu on right click on function to generate this docstrings template !
Note: Any really big stuff will have to wait until after 8.3.0, so don't expect a lot on this topic for a while. But, a dependency bump in the bundled library did get a few little niceties I think you'll all appreciate; these will be in the nightly tomorrow and in 8.1.38 full:
Yay!
This is awesome!
--runs to recommend upgrade solely for this function--
I actually did just that after reading the patch note !
I do this all the time in PyCharm because of this haha
Looking forward to upgrading! In a few years' time, knowing our end users 
yes please! that looks mint
