Our purpose of js encryption is to hope that others cannot modify it. Then we can work hard on the complexity of JS and use modular development. This function refers to that function, and this object inherits from that object... and it will soon be dizzy... Of course, it will also be dizzy when debugging or modifying it yourself in the future... I will just talk about it... Don't hit me...
Actually, what I want to say is that if you don’t want others to modify it, you can add a check of your own validity in many positions in JS. If it is not right, then start calling here to get rid of others...
Of course, whether this check is hidden and whether the aftermath is perfect is what the programmer thinks carefully about. I just give an idea. Here is an example, just expressing the idea, haha...
IE Only
[Ctrl+A Select all Note:Introducing external Js requires refreshing the page before execution]
FF Only
[Ctrl+A Select all Note:Introducing external Js requires refreshing the page before execution]
Actually, what I want to say is that if you don’t want others to modify it, you can add a check of your own validity in many positions in JS. If it is not right, then start calling here to get rid of others...
Of course, whether this check is hidden and whether the aftermath is perfect is what the programmer thinks carefully about. I just give an idea. Here is an example, just expressing the idea, haha...
IE Only
[Ctrl+A Select all Note:Introducing external Js requires refreshing the page before execution]
FF Only
[Ctrl+A Select all Note:Introducing external Js requires refreshing the page before execution]