By WalkingTree   July 08, 2020

Exterminating bugs in your Ext JS app

Sometimes we need to inspect a particular Ext JS component we have instantiated for debugging purposes. Two of the hottest development tools available to any web developer, Visual Studio Code (VSCode) and Google Chrome, seamlessly integrate to provide the most comprehensive debugging environment known to Javascript.

Let’s take a look at some of the most common questions in regard to the debugging of Ext JS applications.

  • Can you provide a classical example that spotlights on the security aspect of web applications?

Security for an Ext JS app is the same as any browser application. Whether it’s vanilla JavaScript or any other framework. Let’s take an example here, the user authenticates, the backend issues a token, and that token is sent back to every subsequent request. The backend then inspects the token to make sure it hasn’t timed-out. This is the same for any framework.

  • How can we detect memory leakage in the solution?

Chrome has a lot of powerful debugging tools to detect memory leaks.

  • Which option should be used to access a component? “id” / “itemid” / “reference”?

For the debugging process, any of these options can be used. Check out Sencha’s latest webinar recording on ‘Exterminating Bugs in Your Ext JS App’ for a better picture of how to effectively debug your Ext JS application.


Privacy Preferences
When you visit our website, it may store information through your browser from specific services, usually in form of cookies. Here you can change your privacy preferences. Please note that blocking some types of cookies may impact your experience on our website and the services we offer.