Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VAR_INVALID_NAME false positive with number-suffixed names

See original GitHub issue

if (urlScope.keyExists('id2') && isNumeric(urlScope.id2)) {
	route &= '/:id2';
}

[INFO]: [cflint] VAR_INVALID_NAME: Variable id2 is not a valid name. Please use camelCase or underscores.

Using CFLint v1.3.0.

Issue Analytics

State:
Created 6 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

ryaneberlycommented, Jan 9, 2018

This has been a ‘feature’ almost since the beginning. I had to disable or change almost a dozen tests after I fixed this one. 😃 However, I agree that ending a number should not be considered invalid naming.

0reactions

timbeadlecommented, Jan 9, 2018

Thanks @ryaneberly for the quick turnaround 😄

Top Results From Across the Web

False positive `invalid-name` when using assignment ...

It makes sense to me that variables scoped entirely within the comprehension can have shorter names, but that's not what's happening here. The ......

What's New in Pylint 2.13

Added new checker typevar-name-missing-variance . ... Fix false positive for unused-import when disabling both used-before-assignment and ...

Configuring a registry - Docker Documentation

Defaults to false . Note: age and interval are strings containing a number with optional fraction and a unit suffix. Some examples: 45m ......

Pylint configuration

#rcfile= # When enabled, pylint would attempt to guess common misconfiguration and emit # user-friendly hints instead of false-positive error messages.

Database Engine events and errors - SQL Server

Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.