Hi Tyler,

We currently have some issues with Javascript highlighting. However we have plans for the nearest future to provide Javascript highlighting everywhere.

I'll let you know once we will include it into any sprint or if there will be any news.

Thanks,

Vladimir

Alright. Thank you for the response. I'm definitely enjoying the IDE overall and look forward to the enhancements in the future!

Hi Tyler,

Just a quick update - I'm pretty sure that we'll include full proper JS highlighting as a part (or before) of our Lighting release that we're going to complete somewhere in late October - early November. But if it'll be possible we'll do our best to work on JS highlighting beforehand and release it asap.

Thanks,

Vladimir

Thanks for the update Vladimir. 

It's great to know that a dedicated developer team is working on this and willing to frequently update users on the status of the project. Great job guys, keep it up!

Glad to know you are working on this. Most of our development is in JS and so the lack of any basic highlighting is a pretty big issue, preventing whole-hearted adoption.

I'm looking forward to seeing this too. This is the only feature that is currently lacking for me as I work with clients who rely heavily on JS customisation. I'm very happy with the rest of the IDE though :)

Hi guys,

Thank you, for remaining in touch!

We have not deviate from our plans. This feature is already in our current working plan within the scope of our new supporting of Lighting components.

In just several weeks you will have an ability to use JS syntax highlighting.

Thank you,

Kate

Hey guys!

Not to be a pest - but do we have any solid date on when this feature will be implemented? I know it was said that late October - early November would be the estimate. Are you thinking as early as next week or maybe closer to mid-November?

Thanks for the hard work!

Tyler

Hi Tyler,

Thank you for your question.

We are agree with you that it's time to announce a more precise date for releasing this feature.

One of the releases with the bases of support of the Lightning components is going to be in the next few working days.The implementation of the Javascript syntax highlighting however will be finished closer to mid-November.

Thank you for using The Welkin Suite,

Kate

Thanks Kate,

My coworkers and I are excited to see it! Can't wait.

I'm looking forward to this feature as well!  I've been impressed with the work so far. 

Hey guys, Just checking in on this feature. Still really excited to have it, any news on the status here?

Hi.

Yes, we have some news.

The Javascript syntax highlighting is on the stage of the internal testing. If everything goes on good it will be released at the beginning of the next week. It will be supported in the static resources and the lightning components.

The work on the javascript will not be stopped on this: in the next couple of sprints we will release the improved highlighting and Code Completion for it.

Just several days)

Thank you,

Kate

Hi guys.

Finally Javascript syntax highlighting is available in The Welkin Suite.

Update your version to the newest one (0.24.11) and you will get this in the code.

As usually all the details related to the feature are present in our blog post.

Regards,

Kate

Hi there Kate,

Awesome new feature! It still has some caveats though: 

If we take the following line:

$.templates("<a id='" + panel + "-minimize'><i class='fa " + minimizeIcon + " fa-2x fa-fw' title='" + title + " paneel minimaliseren/maximaliseren'></i></a>" +

This is shown as:

As you can see, the parser has difficulties in seeing where a string starts, and when its a string inside of a string with the use of ' and ".

It gets even worse on a multiline script:

$.templates("<tr class='clickable-leave-row' data-href='" + baseUrl + "/{{:~retUrl()}}'>" +
"<td>{{:~normalizeVerlofDate(hr2d__StartDate__c)}}</td>" +
"<td>{{:~normalizeVerlofDate(hr2d__EndDate__c)}}</td>" +
"<td class='text-right'>{{:hr2d__Hours__c }}</td>" +
"<td class='hidden-xs'>{{:hr2d__Leave__c}}</td>" +
"<td class='hidden-xs hidden-sm hidden-md'>{{:hr2d__approver1__r.Name}}</td>" +
"<td>{{:hr2d__Workflowstatus__c}}</td>" +
"</tr>");

becomes:

Hi Ron,

Thank you for your post and the detailed example.

I’ve added this bug to our Backlog.

It is included to our current sprint and is already in progress.

Thank you,

Kate

Thanks for implementing this guys. Seems to be working well! Great job.

Hi.

Thank you for your feedback!

This is important for us.

Regards,

Kate

Hi Kate,

After the latest version it seems you guys have made great progress with the javascript parsing. Unfortunatly it seems you guys missed one thing from the string parsing: escaped quotes.

If you escape a quote Welkin Suite doesn't pick up on the fact it shouldn't count that quote for the string but the next one:

"<a href='javascript:navigateUrl(\"" + baseUrl + "apex/apexClass?id=" + Id + "&retUrl={{:~retUrl()}}\")' role='button'><i class='fa fa-plus fa-2x fa-fw' title='Title'></i></a>");

The following example goes wrong after the functioncall navigateUrl(\""

Hi Ron.

Thank you again for you bug report.

I've added this issue to our backlog.

Our team will fix this as soon as possible.

Thank you,

Kate