Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inspector - misc #3570

Merged
merged 3 commits into from
Nov 4, 2023
Merged

Inspector - misc #3570

merged 3 commits into from
Nov 4, 2023

Conversation

vemv
Copy link
Member

@vemv vemv commented Nov 4, 2023

Cheers - V

@vemv vemv requested a review from bbatsov November 4, 2023 18:02
cider-inspector-max-atom-length
cider-inspector-max-coll-size
'v2)))
(when (nrepl-dict-get result "value")
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to do this v2 refactoring which keeps backward compat.

All of the inspector usage here was coupled to the "value" attr, which was hindering access to other attrs (the "doc-fragments" attr in particular, which needs separate tratment given that it's processed through cider--render-docstring)

|===
| Action | Description

| kbd:[click] or kbd:[p]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not "i" for "inspect"?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cider-debug has bound:

["Inspect current value" (cider-debug-mode-send-reply ":inspect") :keys "p"]

, so it would seem consistent.

However we could use both p and i - seems harmless given that this keymap is constrained to a single given string.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that'd be good. I'm guessing the debugger couldn't use i as it was already taken by inject. Lots of functionality got weird keybindings if it was added later in the lifecycle of the project and the natural keybindings were already taken by something else.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added i!

@vemv vemv force-pushed the inspector-nov-refinements branch from b0e4199 to ccf0b1c Compare November 4, 2023 20:58
(insert (format "%d. " num)
(propertize note 'font-lock-face 'font-lock-comment-face) " "
(propertize class 'font-lock-face class-face)
(propertize class 'font-lock-face class-face 'mouse-face 'highlight)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bbatsov - added 'mouse-face 'highlight following Slack feedback

@vemv
Copy link
Member Author

vemv commented Nov 4, 2023

I tried the refactored defuns one by one and they keep working as usual - merging

@vemv vemv merged commit bbef4f4 into master Nov 4, 2023
26 checks passed
@vemv vemv deleted the inspector-nov-refinements branch November 4, 2023 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Streamline navigating from *cider-error* to the inspector
2 participants