I doubt I’m alone in using the KTL Library, as it adds much needed functionality to the platform that lets us keep our customer’s on Knack.
After this morning’s app outage due to a conflicting change published by Knack with the KTL Library, I’d like to kindly request that the Knack Development team add the KTL Library to one of their apps in their test environment so that in the future if they make an app breaking change it can be evaluated in advance and the relevant party can be notified.
The objective is to give the third party developer who maintains this library for FREE enough of a lead time to fix any conflicts or issues BEFORE your customers who use this library’s apps stop responding in the middle of a work day.
Agreed, @Kara, I’d greatly appreciate anything you can put in place to avoid these breaking changes in the future.
Thankfully @NormandDefayette_CortexRD was available to respond quickly.
It would definitely be nice to get a dev log somewhere, that’s also a good call.
Also, I just to be clear, because KTL has a vast feature set, my recommendation is just a simple pass/fail check on whether or not the changes being made by Knack’s Development Team breaks Knack when the Library is loaded/present. It isn’t to test or check if KTL functionality is working as expected.
I will through in my had into this request as well! KTL has completely transformed my app (Thanks to @CSWinnall and Amanda)! While I wasn’t personally effected this time, this is something that I am worried about. Adding some basic go/no go tests would be fantastic.
For some reason I doubt that some knack devs DON’T use the KTL
