fix(scanner): support multi-line variables

[jippi]

Fixes #40

[jippi]

@intentionally-left-nil does this fix your use-case? :)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.58%. Comparing base (ab39e27) to head (152aeeb).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
+ Coverage   68.54%   68.58%   +0.03%     
==========================================
  Files          66       66              
  Lines        3462     3466       +4     
==========================================
+ Hits         2373     2377       +4     
  Misses        959      959              
  Partials      130      130              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[intentionally-left-nil]

@jippi it does fix it 👍

although I'm a bit surprised you didn't need to fix the Token struct in order to account for multiline pieces. I didn't dig too deeply into the repository, but it might be worth fixing that, ripping out the Token length/offset fields, or having a new MultilineToken struct

[jippi]

The token struct should be fine to point to the first line of a multi-line statement; its only used to provide useful feedback errors to end-users; so you would get the error line reference pointing to the line where the key= part is - which is the place you likely would want to jump to anyway.

The range itself isn't wouldn't really be used for anything.

Also, the parser keeps track of first/last line of a token; so it should be rolling it up nicely where applicable