None validator incorrectly handles numeric arguments

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.

@quietone thanks for uploading a tests-only patch so can see that the fix indeed does work.

The change made looks good. Agree checking if the number is_numeric makes all the sense in the world haha.

However, I would have expected that a numeric argument would have the Numeric validator, not the None validator. Perhaps that is the underlying problem?

I think that the None validator is used for literally everything, when no argument validation is set. So the problem is that without this code it would cause issues with the numeric validator. I think really it should not have to know which argument it's dealing with - i.e. why is it doing any validation at all if validation is set to none?

Re-titling since the undefined variable was dealt with elsewhere already.

I think we should open a follow-up for #72 - i.e. can we move plugin-specific code out of the None validator or at least better document why it's there.

Opened 📌 Re-evaluate numeric validator Postponed: needs info