Is there a way to keep one bad Javascript call from breaking my entire code base? Right now, if someone in my app makes a bad Javascript call, then the script in the rest of the application stops working.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a way to keep one bad Javascript call from breaking my entire code base? Right now, if someone in my app makes a bad Javascript call, then the script in the rest of the application stops working.
You can use Exception Handling to attempt to work around this problem – in particular,
tryandcatch. That would be most effective if there are particular areas of the application that are fragile and that seem to break most often.But this might just be a symptom of a larger problem. If you find that your application is broken on a regular basis, the problem could lie with your development process. Perhaps you need to develop functional/unit tests, test your application more rigorously prior to deployment, understand why individual developers are not fixing their own mistakes (or “releasing” so many in the first place), etc.