Release/1.1.0

[krvajal]

After merging #47 #46 we can release a new version.

Release checklist

• Update changelog
• Fix failing CI
• Merge PRs (Fix extension activation events not been triggered  #47, Fixes pre-preocessor directive highlighting #46) into this branch
• Merge into master, tag and release new version

[pedro-ricardo]

@krvajal, still don't know if i got this right but i'm running the extension tests:

npm install
npm run vscode:prepublish
npm run lint
npm test --silent

And all the tests are passing, but the problem seems to be that this command npm test --silent never ends ... and that's why Travis-CI can't approve. They have a 10min time limit.

CI log:

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Still studying how to write this tests

[krvajal]

Try to run the tests locally and see if you can identify which one is taking longer than expected. Get Outlook On Sat, Apr 14, 2018 at 4:51 PM +0200, "Pedro Ricardo C Souza" <notifications@github.com> wrote: @krvajal, still don't know if i got this right but i'm running the extension tests: npm install npm run vscode:prepublish npm run lint npm test --silent And all the tests are passing, but the problem seems to be that this command npm test --silent never ends ... and that's why Travis-CI can't approve. They have a 10min time limit. CI log: No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself. Still studying how to write this tests — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[pedro-ricardo]

Not sure if it is a fix ... but returning the index.ts file to the original one from VSCode tutorials seems to solve the issue. All tests are performed and passed, and the npm test command exits normally. If you consider this a fix i can make a commit so you can see.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@3af3ea4). Click here to learn what that means.
The diff coverage is 17.39%.

@@            Coverage Diff            @@
##             master      #48   +/-   ##
=========================================
  Coverage          ?   13.21%           
=========================================
  Files             ?        9           
  Lines             ?      348           
  Branches          ?       49           
=========================================
  Hits              ?       46           
  Misses            ?      302           
  Partials          ?        0

Impacted Files	Coverage Δ
src/lib/helper.ts	0% <0%> (ø)
src/features/completion-provider.ts	0% <0%> (ø)
src/features/document-symbol-provider.ts	0% <0%> (ø)
src/features/hover-provider.ts	0% <0%> (ø)
src/extension.ts	0% <0%> (ø)
src/features/linter-provider.ts	0% <0%> (ø)
src/lib/tokenizer.ts	100% <100%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3af3ea4...0724956. Read the comment docs.

[pedro-ricardo]

Not sure why, but nether of the highlight changes me and kgerheiser proposed are in the 1.1.0 release in vscode extension. But i can see them when I run the extension through extension host in master branch.

[vkbo]

I came here looking for the pre-processor highlighting. It doesn't work for me either with the version installed via vscode.

[pedro-ricardo]

Yes, we are experiencing some problems with the release, if compiled locally in the master branch, the extension have the new pre-processor highlighting fix, although when installed with VSCode it doesn't have the correction. We are looking into it.

[krvajal]

What version of the extension do you have installed? Is it 1.1.0 or 1.1.1

[vkbo]

I have 1.1.1 installed.

It currently looks like this:

The main issue is that it interprets the endif as a fortran endif, otherwise I'm not particularly concerned with the pre-processor lines not being highlighted.

[krvajal]

It was a mistake on my side. I made the release while been on the wrong branch so the changes were not reflected properly. I have published a patched version (1.1.2) that should solve the issue. Please let me know if this is the case.
And please move the discussion to an issue and not as part of the PR.