Debugging with the KBX extension: how to avoid the need for deployment with every code modification?

I am currently debugging my applications so that they can work with the KBX extension. The KBX extension launches the latest deployed version , so every time I change the code in the application, I need to redistribute it to see the changes. Can the Kynetx team provide us with a modified KBX extension that uses the latest saved version ?

+4
source share
2 answers

We have plans to make KBX more understandable for developers, but at the same time there are a few tricks.

We recommend that you spend most of your development time testing using bookmarklets, as this gives you more control over when your actions fire, making it easier to check the status of the page before and after your rules fire. Applications can be tested using bookmarklets without changing the code and are easy to use.

This does not help to debug in the rare case that your application behaves differently while working in KBX, but it should go past most of the problems that you are currently experiencing.

+3
source

Here's the solution for Chrome and Firefox : a modified KBX extension for the latest version of applications: http://blog.lolo.asia/technology/kynetx/2011/04/16/debugging-with-kbx-extension-how-to-avoid -having-to-deploy-at-every-code-modification /

In short, I replaced:

KOBJ.add_config_and_run ({"gets rid of: response.apps});

with:

//patch run_latest_app_version_in_kbx var run_latest_app_version_in_kbx= true; var run_msg_json={'rids':response.apps}; if (run_latest_app_version_in_kbx===true){ for (var i=0;i<response.apps.length;i++){ run_msg_json[response.apps[i]+':kynetx_app_version']='dev'; } } KOBJ.add_config_and_run(run_msg_json); // 

in page_interaction / pages.js inside the Chrome extension and in resources / jid 0-njkmo4quo4rc8p9kcuemahnyiku-kynetxforfirefox-data / page_interaction.js inside the Firefox extension

+1
source

All Articles