Semantic Highlight Improvement for Python #233

[SmitAkbari26]

Apologies for the delayed response, as I haven't been actively checking GitHub lately.

I solve this self parameter lose its highlight when semantic tokens are enabled issue and create new pull request please check new pull request and let me know.

[SmitAkbari26]

Please check new commit 67c0e94
@wesbos @palashmon

[rennsax]

@SmitAkbari26 Could you please wait for a moment before I spare my time to push my commits? I have made some enhancements for Python semantic highlighting which are also harmless to other languages. You can check the feature in semantic-highlight-guide.

[SmitAkbari26]

@Eitheages Ohk i will close mine new pull request and add your new commit.

[rennsax]

@SmitAkbari26 You can check my commits here. I'd love to keep communication with you!

[SmitAkbari26]

@Eitheages I am glad to here that i will check your commit and let you know.

[SmitAkbari26]

@Eitheages,
Your change is good but it got same issue which i previously solved and merge it.
This is look after i solve issue

And with your change it create same issue which previously have

[rennsax]

@SmitAkbari26
Maybe you can open semantic token feature? This could happen if VS Code doesn't recognize the word as a valid function/property. I always open my Pylance extension and enable semantic highlighting.

But it reminds me that I should consider the scenario when semantic highlighting is disabled. I've reverted your previous PR (#223) (forgive the possible impolicy), so the problem above occurs again.

I'll try to fix it when I'm available again!

[SmitAkbari26]

@Eitheages Ohk. Try to solve error and send me latest commit you make i will check it.

[rennsax]

@SmitAkbari26 May I commit on your branch tip?

[palashmon]

Not sure if we can do this, as this change will affect all languages not just Python.

[rennsax]

I opened my PR #236.