Explanation
Was following this post yesterday by @RPGIS and it seems that I'm not alone in hating the Arcade IDEs that are shipped with ESRI products. It also seems that most people in the community use the same workaround of copying the code from the ESRI IDE, pasting into a real IDE, then pasting back into ESRI IDE.
This workflow is an absolute pain in the butt for any complex Attribute Rule configurations and a recipe for losing track of what versions of scripts live where.
So I took it upon myself to distill some of the personal practices I use into a Python package/script that automates the extraction and insertion of plaintext Arcade into file databases with
