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.

#NumberRange only visible in debugging/logging?

See original GitHub issue

I have seen #NumberRange in the verbose logging output, and throughout the source code, but can’t seem to be able to use to it in any way. Possibly a bug?

I noticed it also gets tagged as a #Value in the verbose log but then disappears

I suspect it’s because the contraction 1-2 gets expanded to 1 to 2 so the original tags get lost somewhere?

// verbose
> nlp('1-2 kg')
 kg   + Unit 
 kg   + → Noun 
1-2  + Value 
1-2  + NumberRange 
1-2  + → Contraction 
 kg   + Singular 
 kg   + → Noun 
 to   + Conjunction 
 
> nlp('1-2 kg').debug()
'[1]'     -  Number, Cardinal
'[to]'    -  Conjunction
'[2]'     -  Number, Cardinal
'kg'      -  Unit, Noun, Singular

> nlp('1-2 kg').has('#NumberRange')
false

> nlp('1-2 kg').match('#NumberRange').text()
""

Issue Analytics

State:
Created 4 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

2reactions

spencermountaincommented, Jan 26, 2020

great find. Thanks Jake. Yeah, the logic about keeping existing tags during .replace() changed in v12. Good observation that it got tagged as a NumberRange briefly. got it fixed on dev. And as Dominic said, it should be released this week. cheers

0reactions

spencermountaincommented, Feb 7, 2020

fixed in v13.0.0