Fix case class/object highlighting #14
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Hi maintainers,
Problem. The
casekeyword is assigned the scopekeyword.control.flow.scalain the declarationscase classandcase object. This seems incorrect. See the image below.Proposal. After investigating, I discovered that the corresponding pattern did not account for whitespace between the
casekeyword and theclass/objectkeywords. To fix this, we propose two changes in this PR:caseandclass/objectdeclarations andtraitdeclarations because they cannot be preceded by acasekeyword.The image below shows the result after these changes have been applied.