Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix exception reported in #447 #536

Merged
merged 66 commits into from
Jan 9, 2018
Merged

Fix exception reported in #447 #536

merged 66 commits into from
Jan 9, 2018

Conversation

MikhailArkhipov
Copy link

@MikhailArkhipov MikhailArkhipov commented Jan 5, 2018

Incorrect use of indexer on non-array
Added some more tests

Closes #447, #423

@codecov
Copy link

codecov bot commented Jan 5, 2018

Codecov Report

Merging #536 into master will decrease coverage by 0.15%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #536      +/-   ##
==========================================
- Coverage    56.4%   56.25%   -0.16%     
==========================================
  Files         212      212              
  Lines       10018     9978      -40     
  Branches     1762     1754       -8     
==========================================
- Hits         5651     5613      -38     
+ Misses       4362     4360       -2     
  Partials        5        5
Impacted Files Coverage Δ
src/client/providers/completionSource.ts 94.28% <100%> (+1.74%) ⬆️
src/client/telemetry/index.ts 81.08% <0%> (-5.41%) ⬇️
src/client/common/installer/pythonInstallation.ts 100% <0%> (+4.68%) ⬆️

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 321e204...10e0a80. Read the comment docs.

Copy link
Member

@brettcannon brettcannon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I asked to have the description of the tests fleshed out, but I trust you to do it properly so I'm approving ahead of time. 😉

@@ -16,7 +16,7 @@ suite('Language.Tokenizer', () => {
assert.equal(tokens.count, 0);
assert.equal(tokens.length, 0);
});
test('Strings', async () => {
test('Strings 1', async () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible to have a more descriptive string from the test? For example, I don't know how this is different from 'Strings 2' so I don't what I need to make sure not to change in the test so I don't break what it's meant to be testing.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll try :-) have hard time coming up with names...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean it can be rather wordy since it is a test. Basically come up with a sentence to explain to me why you wrote the test and make that the test name.

@MikhailArkhipov MikhailArkhipov merged commit 7f2c239 into microsoft:master Jan 9, 2018
@MikhailArkhipov
Copy link
Author

This most probably addressed by #536 coming with the next update.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Linter throws errors
2 participants