# Script Library Formatting and Documentation

**URL:** <https://forum.inductiveautomation.com/t/script-library-formatting-and-documentation/82056>\
**Category:** Ignition\
**Tags:** ignition81, scripting\
**Created:** [November 17, 2023, 3:48pm UTC](https://forum.inductiveautomation.com/t/script-library-formatting-and-documentation/82056 "2023-11-17T15:48:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 17, 2023, 4:43pm UTC](https://forum.inductiveautomation.com/t/script-library-formatting-and-documentation/82056/3 "2023-11-17T16:43:14Z")

</div>

If you're on 8.1.19 or higher, project library scripts with "docstrings" per Python convention _do_ show up in the autocomplete in other editors:  
[https://docs.inductiveautomation.com/display/DOC81/Scripting+in+Ignition#ScriptinginIgnition-SystemFunctions,Hints,andAutocomplete](https://docs.inductiveautomation.com/display/DOC81/Scripting+in+Ignition#ScriptinginIgnition-SystemFunctions,Hints,andAutocomplete)

If you're on 8.1.32 or higher, if you author those docstrings according to Google's Python style guide, you'll even get nice argument and return value descriptions.

---

_[View the full topic](https://forum.inductiveautomation.com/t/script-library-formatting-and-documentation/82056)._