racket / racket/drracket

Inlay hints (aka Parameter hints)

Open
#557 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
516
Forks
103
PR merge metrics
No merged PRs in 30d

Description

https://github.com/jeapostrophe/racket-langserver/issues/29

Inlay Hints

(bug regarding wrong argument order)
https://github.com/racket/racket/commit/96f26e0a3576f0c67c17d9ee6faeee899494b1f0

Rendering inlay hints would be very useful, eliminating a lot of the guess work of function arguments and struct fields without needing to look at the documentation or the definition again and in the case of structs, creating functions with keyword arguments to see what the fields are.

(struct person (firstname middlename lastname age job))

; when constructing, it will render the field names as a sort of "background image", 
; the code that actually is ran is the valid amount of arguments, so (person "bob" "j" "smith" 20 "programmer")

(person firstname "bob" middlename "j" lastname "smith" age 20 job "programmer")

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked racket-langserver issue and the referenced Racket commit about argument order. Use the struct example and inlay-hints screenshot as behavior references; done means DrRacket renders useful parameter and struct-field hints without changing the executed argument list.

Written by the indexing model from the issue text.

Assessment

Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.