[RFC] JSDoc for hovering

[ssssota]

ref. #135 #44

To inspect CSS definition from your JS files.

Same aproach as #44 and refined it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4cae3a4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mizdra]

This PR looks like a draft. Is there anything you would like me to do? Should I review the PR immediately, or should I wait until it is no longer in draft status?

[ssssota]

I forgot to mention that it was in draft for self review.
This PR is ready for review. Please review it!

[mizdra]

@ssssota I checked the behavior of this change. As a result, I found the following pros and cons.

Pros

• Users can easily preview definitions in VS Code.
  • The preview is triggered by simply hovering over the definition.
  • It is easier than Definition Context for Hover Info #197.

Cons

• It is not a common way to implement definition previews.
  • It may not work properly in some editors.
• Value declaration preview does not work correctly.
  • See [RFC] JSDoc for hovering #179 (comment)
• Indentation of nested rules is incorrect.
  • 

---

After evaluating the overall situation, I believe that #197 is the better implementation method. I will close #179 and continue working on #197.

This Pull Request will be closed, but the ideas gained from it were very inspiring. Thank you for your contribution!