So, I have now learned when my code is messed up, I get something like this when I try the intended action and do not get the right results.
This IS obviously very helpful and guides me to review my work. Sometimes however as you can imagine, that custom bit of coding is many many lines long, especially the way Wix code displays. IT WOULD BE SUPER DUPER AWESOME if we could end up getting more details, especially for the TypeError deals or .show is not a function type errors when I am missing a # or " in that line, that these errors REFERENCE THE LINE NUMBER so I can easily find and fix these.
Mind you here, I was editing code quickly and must have misstyped something in accidentally, but it is going to take so much longer to find where I mis-hit an extra e and what it replaced that is now breaking the code entirely. That line number reference could greatly help. I know it can be done, because the system clearly sees what is the error and where it is, it just so far does not report it back to me and makes me go back and sift through until I find it. Let’s hope I don’t miss-hit something else during that process.
Just more UX love requests 