Thx.
Thank you, I’m sure it will be worth the wait! Would it be possible to put out a forum post or email when it’s rolled out again so we can be aware of any changes please?
I appreciate the quick response to all the feedback, thanks for getting on a solution so fast.
@allon-schamroth can you please share a link to your site?
I’d like to learn why you got the message ’ Property ‘items’ does not exist on type ‘any[]’
Maybe can add a feature to “dismiss” the “bug”. So the red line wont show up again next time until edits it made on that line
I don’t think that’s a good solution. The error marks are needed. They just have to be correct. If you didn’t think you’d need error marker, you could edit your code in notepad.
This thread stops on Feb 3. It is now Mar 15.
What is the progress on fixing false error reporting in the WIX editor?
Currently, this simple reference to a legitimate element:
$w( ‘#dropdownMember’ ).selectedIndex = 0 ;
Elicits the following error marking in the editor:
‘#dropdownMember’ is not a valid selector
In fact all the references to elements are marked on some of my pages, but not all pages. The pages with these markings work just fine.
What is happening here?
@bill I’m referring this to QA for evaluation.
Hey,
We worked to fix the issues you reported here a while ago.
- Some bug fixed.
- We improved the performance of the completion widget.
- In some cases, you may see errors in the code editor for existing code that is running on the live site. It is our way to direct you to code better as some patterns work in some cases and in other cases fail.
Your feedback is welcome.
Shay
@russian-dima , @allon-schamroth , @volkaertskristof , @certified-code , @Rory
Hey,
We worked to fix the issues you reported here a while ago.
- Some bug fixed.
- We improved the performance of the completion widget.
- In some cases, you may see errors in the code editor for existing code that is running on the live site. It is our way to direct you to code better as some patterns work in some cases and in other cases fail.
Your feedback is welcome.
Shay
@russian-dima , @allon-schamroth , @volkaertskristof , @certified-code , @Rory
ok, thanks for info.
So are these errors that show up throughout my code a false alarm, or do I need to change the syntax? I see it was recommended above in early February to just wait and the errors will go away, but it’s now late March.
The code seems to work, and I tested it ok myself, but just before I tested it, a customer submitted the form, and most of the form results did not come through in the SendGrid email, so I am wondering if these errors are what caused the issue that time?
Yes it is a FAKE-ALARM (bugs which still have to be fixed).
I have an BUG-EXAMPLE, too…
My global variables in this example are…
var selectedElementID
and…
var selectedIndex
…but one of these is underlined in red (although everything works fine).
Perhaps choosing another color for such WARNINGS???
$w('Button').onClick(async(event)=>{//console.log(event.target.id)
let buttonLength = await event.target.length
selectedElementID = await event.target.id
selectedIndex = await selectedElementID.charAt(selectedElementID.length-1)
if (selectedElementID === "BTNsearch"){manual_Search()}
else if (selectedElementID.substring(0,selectedElementID.length-1) === "BTNresetCBG"){
MEMcboxes[selectedIndex-1] = []
$w('#'+CBpräfix+(selectedIndex)).value = undefined;
local.setItem(CBoxes[selectedIndex-1], undefined)
FILTER_ENGINE(myValue)
}
Also this one do not eliminate the bug…(still marked in red as failure-code)
MEMcboxes[(selectedIndex-1)] = []
@russian-dima Thank you! That’s good news because I wrote that code a year ago, and I really don’t want to work on it again, LOL!
@phurlston
You don’t have to rework your code. Everything should be allright with your code.
It is just an UPDATE of the —> “Code-Completion-Widget” in the CODE-Section of your Wix-Editor.
Now you should be able to see more options, when writting some code.
A very useful feature and i hope all bugs will be eliminated as soon as possible.
A THANKS goes to wix/velo for this update/work!
@coz You should show all your errors, so the wix-team is able to hunt all the bugs 
Same Problem here, woke up to a code (which was working perfectly and had no red markings yesterday) with more than 50 errors!
Is there a timeline for this fix of the ‘false alarms’ ?
@shay-wix I noticed this issue on Feb 1, 2021 as well. It started happening to all of my websites again in the editor 3 days ago. Last time, the false errors went away, with no changes on my end, after a few days. However, during that period, I was unable to publish anything as whatever I published, even though the code was correct would error on the live site. Extremely frustrating to be in this situation. When will this be fixed?
As a reply to my own post above, I was having problems with emails being sent from my Wix code through SendGrid, and I was worried it was related to these false errors. The body of the email messages were being randomly truncated on some emails submitted through my custom form, and I couldn’t duplicate the problem.
Well, it wasn’t the false code alarms above after all. The code still works fine, as @russian-dima said it would, and my problems with the SendGrid emails were not related.
In case anyone is interested, the issue with SendGrid occurs whenever anyone types an “&” in one of the text field variables that is used to populate the email message.
Some people use & in their company names and titles, so it was very random, and I couldn’t repeat the error because I didn’t see the “&” since the email was being truncated.
Once I stumbled on the cause, I was able to use a post on this forum to automatically replace “&” with the word “and” in my code before sending the email. Problem solved.
I didn’t know that about SendGrid. Hopefully this info helps others that are using Wix variables in their messages sent through SendGrid.
Some UPDATES on this after about 3-month?
https://www.wix.com/velo/forum/coding-with-velo/some-news-about-the-code-completion
I’ve also got errors all over the place that are stopping the application from working:
-dataset.new is no longer allowed
-I cant’s assign the value of an input box set to type “number” to a variable which is of type number.
-I can’t assign a field of an object to a variable of type date.
This all worked and now doesn’t.