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

IntelliSense AutoComplete in SWQL Studio Not Working Properly After Upgrade to 3.0.0.290 #264

Open
jHumeLPL opened this issue Dec 23, 2020 · 5 comments
Assignees
Labels

Comments

@jHumeLPL
Copy link

I was on 2.6.238.0 prior to this and IntelliSense worked great. It would fill in table and column names perfectly for me, even if I aliased the table names to something else it still worked great.

Now, after upgrading to 3.0.0.290, the only auto-complete feature in SWQL Studio that works is Functions. No table names or column names pop-up in the autocomplete, it doesn't matter if I've aliased a table or not. It just doesn't work now.

I have checked to make sure my preferences are still set. I've also tried toggling the settings off and on and I've tried restarting SWQL Studio. Still not working.

@jHumeLPL
Copy link
Author

So I just tried installing the latest version from March (SWQL Studio version 3.0.0.309) and Intellisense still isn't working properly. But as soon as I go back to the old 2.6 version it works fine again.

Is nobody else having this issue or somethig?

@nothrow
Copy link
Contributor

nothrow commented Apr 26, 2021

I'm not aware of any change that should've caused this issue - I will check and find what is responsible.

@nothrow nothrow self-assigned this Apr 26, 2021
@nothrow nothrow added the bug label Apr 26, 2021
@nothrow
Copy link
Contributor

nothrow commented Apr 26, 2021

Thanks for reporting this. The issue lies in small change that actually made the autocomplete case sensitive - and since lot of people are used to write everything lowercase, noone noticed before.

Fix in PR #278. Release will follow once the PR is approved.

@martin-vw
Copy link

I'm not sure how to read the comment on the pull request to know if that is indicating that the issue is fixed. I'm still seeing the problem on versions: v3.0, v3.0.0.309-beta. When I switch back to lower versions it works.

Example:
SELECT N.xxxx FROM Orion.Nodes N

In the previous versions if I enter the N. I can start typing column names and IntelliSense would provide the matching column names.
intellisense

@danjagnow
Copy link
Contributor

The fix is incorporated into the v3.0.336 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

4 participants