Bug: Parser interpretes string id with starting with number followed by 'e' as exponenets about surrealdb

[Vignesh1-art]

I would like to work on this issue please. I have done analysis.
Here

surrealdb/core/src/syn/lexer/number.rs

Line 79 in 51aea4f

x @ (b'e' | b'E') => {

if you check after parsing number it comes that line and then tries to parse -,+ or numeric digit.

I can make changes in parser to expect alpha numeric character after 'e' . But how this needs to behave if I encounter - or +?

I need some suggestion on how to fix this issue please.
Thank you :)

[DelSkayn]

Hi! Thank you for raising this issue!
I appreciate that you want to contribute a fix. However the lexer is somewhat complex and providing you with the right suggestions would take longer than just fixing the issue myself so I went ahead and did that.

If your interested, the problem was that the lexer returned a token too early. It found a valid number with an exponent and then immediately returned it without checking if there were any alpha numeric numbers immediately after it.