Publish JavaScript Change Logs In Patch Notes, or Put Nintex Forms On Github!
For anyone who is attempting to get their hands dirty inside the more obscure parts of a Nintex Form, it can frustrating to see a patch note that only reads
"This release may include changes of some controls. If you are using custom JavaScript, it may require adjustments to your custom JavaScript."
What would be 1000% better, is if we could get the published / generated version control changes so that we didn't have to guess or hunt to find the changes between updates.
And perhaps even better than that would be if Nintex would create a public repository on a service like Github to allow outside developers to submit changes to the codebase, and to create a better ecosystem of understanding around the complexities of the Nintex Forms code.
I know that something like a Github repo won't spring up over night, but I certainly feel like it might be something to work towards if we can at least get the change logs in the patch notes squared away.
Thank You!

Hi Noah. Thanks for taking the time to suggest this but the overhead of putting code changes into the patch notes is not insignificant.
Our preference is to build the functionality you are using JavaScript for into the product, which you will see through Universal Forms in the future.
If you feel there is a specific piece of functionality you would like to see, please raise a feature request in User Voice and I will reply.
Cheers,
Euan