[DevTools] Make Functions Clickable to Jump to Definition #30769
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a cute short cut and there's precedence in how Chrome prints functions in the console *if* the function's toString would've had a function prefix like if it was a function declaration or expression. It does not do this for arrow functions or object methods. Elsewhere in the JS ecosystem this isn't really used anywhere. It invites more questions than it answers. The parenthesis and curlies are enough. There's no ambiguity here since strings have quotations. It looks better with just its object method form. Keeping it simple seems best.
While this might not be an arrow function it's a common enough annotation for an unnamed function that people would get it.
Hover state makes it a little clearer that it's clickable and follows the pattern of the owner list.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
facebook-github-bot
added
CLA Signed
React Core Team
eps1lon
approved these changes
Aug 22, 2024
There was a problem hiding this comment.
To my eyes this flows better because I'm used to looking at function syntax but not weird "f"s.
Agreed. Just f would also beg the question if we should add async if it is a real async function
Also 👍🏻 for making it a simple link instead of hiding it behind a context menu. That's also why I skipped reviewing #30786 earlier because I simply didn't know this functionality existed.
This was referenced Aug 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently you can jump to definition of a function by right clicking through the context menu. However, it's pretty difficult to discover. This makes the functions clickable to jump to definition - like links.
This uses the same styling as we do for links (which are btw only clickable if they're not editable). Including cursor: pointer.
I added a background on hover which follows the same pattern as the owners list.
I also dropped the ƒ prefix when displaying functions. This is a cute short cut and there's precedence in how Chrome prints functions in the console if the function's toString would've had a function prefix like if it was a function declaration or expression. It does not do this for arrow functions or object methods.
Elsewhere in the JS ecosystem this isn't really used anywhere. It invites more questions than it answers.
The parenthesis and curlies are enough. There's no ambiguity here since strings have quotations. It looks better with just its object method form. Keeping it simple seems best. To my eyes this flows better because I'm used to looking at function syntax but not weird "f"s.
Before:
After:
After (Hover):
