rokucommunity / rokucommunity/brighterscript

Incorrectly reporting errors

Open
#548 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
208
Forks
68
Avg merge
8h 39m
Merged PRs (30d)
39

Description

Operating System: Fedora 30
VS Code: 1.44.0
BRS Extension: 2.1.2

I am getting red squiggle lines under code which is actually correct. It was on a huge non-SG screensaver main.brs, but I can reproduce it at will with the following steps.
$ mkdir test
$ cd test
$ code .

Open a new Untitled file, and then type or paste the following code:

Function RunScreenSaver( params As Object ) As Object
     main()
End Function

sub main()
    print "Entering main()..."
    m.screen  = CreateObject("roScreen")                    ' Required object
    m.port    = CreateObject("roMessagePort")               ' Required object
    di        = CreateObject("roDeviceInfo")                ' For resolution info
    timeStamp = CreateObject("roDateTime")                  ' For elapsed time
    i% = 1

    i% = i% << 3
    i% = i% >> 3

    for j = 1 to 10
        print j
    next j

    for k = 1 to 10
        print k
    end for

end sub

All should look well, until you hit <CTRL-S> and save as main.brs. After writing to disk, the red marks appear, as shown in the attached screenshot below.

There was a red squiggle under the "j" in "next j" but I upgraded the version of VS Code and the extension this morning and I can no longer reproduce that.

My screensaver compiles and runs fine even with the squigle marks.

Screenshot from 2020-04-12 09-56-33

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the diagnostics in VS Code by creating the temporary project, opening an Untitled file, and saving the supplied code as main.brs. Compare the red squiggles with the valid BrightScript constructs shown; done means the editor no longer reports errors for code that compiles and runs correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.