[Script] WME Validator v2021.3.5 (+ PLACES BETA)

[berestovskyy]

AFAIK, there is no bug in Validator.

Why my TODO list is so long then?

And the personnal check should be something as optionnal and for advanced editors

There is no any harm having them available for all editors. The information to match is limited. For instance, there is no way to match editor's name.

Also there is no relation between editor's level and the ability to use regexps. Some people (with IT background, I guess) understand those regexps, some people don't. But anyone can ask for a help and then just copy-paste two lines.

That is what the Custom Check in Validator for - gets the job done. Instantly

[berestovskyy]

This is the area I'm running the report in, if you want to try it yourself.

Both of your regexps work fine with me and give exactly the same number of reported segments.

Make sure you do not put any spaces before the exclamation mark.

[berestovskyy]

EDITED: I think I have narrowed it down to Highliter script. Unless it just magically starting working again.

Ok, cool. At least now you'll be able to switch between one script or another.

Sorry, I have no Mac, so I can't check the issue

[berestovskyy]

Where can I download it? userscripts.org seems not to be working...
For Firefox

As suggested in other thread, here is the working link: userscripts.org

[berestovskyy]

No worries, I guess I can fix #74 for such cases.

[berestovskyy]

Please try Settings->Reset defaults or just make sure your search tab has no options activated.

[berestovskyy]

How would I create a custom expression to flag nodes with turn restrictions?

You can try ${segmentsA/B} and ${outA/B} variables, for example:
Template: ${segmentsA}:${outA}
RegExp: /3:[^3]/

This will match a segment connected to 3 other segments at node A, but having not 3 outward turns enabled.

But it's not that simple. You have to take into account segment's direction etc etc. So I suggest you use instead Shift+Z WME shortcut which shows you disabled turns.

[berestovskyy]

How should I search for segments shorter then 17m?

Try to match length 0-9 OR 1 following 0-6:
Template: ${length}
RegExp: /^([0-9]|1[0-6])$/

[berestovskyy]

userscripts works fine with me: link

GreasyFork: link

[berestovskyy]

Hi!
As we discussed earlier, Validator skips any segment updated after 2014-05-01 and locked for you.

You can still check locked segments updated prior that date, so it does not skip base maps, old edits etc.