-
Notifications
You must be signed in to change notification settings - Fork 176
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
inspect-get-path
op not working as expected
#826
Comments
Thanks. I do not know much about this corner of cider-nrepl. However, it comes to mind that we could include the |
alexander-yakushev
added a commit
that referenced
this issue
Apr 30, 2024
…r reply instead See #826.
alexander-yakushev
added a commit
that referenced
this issue
Apr 30, 2024
…r reply instead See #826.
We're removing this op Line 17 in 81c5d11
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am in cider-inspector on a path printed as
and I call the middleware operation
inspect-get-path
Expected behavior
I would expect that the operations returns the path
"similar" to what I see in inspector, which is :
:foo :bar (nth 3)
but I get something different, which seems strange for 3 reasons:
inspect-get-path
op returns the strings as keysI think the op is currently not used in CIDER in any case, correct ?
I though to use it eventualy here:
clojure-emacs/cider#3549
to get the "current path" instead of getting the current path from the textual result:
https://github.com/clojure-emacs/cider/blob/1090db8a677c2fb1b34aa5e0f591a99abcde3d5c/cider-inspector.el#L318
Actual behavior
Steps to reproduce the problem
cider-inspect a map until the deepest point, the sequence
and then use an interactive function while in the inspector to call the
inspect-get-path
op:will print "Path: ’(bar foo (nth 0))’"
wile I would expect to see:
Path: ’(:foo :bar (nth 0))’
or have it returns outside "status" even.
Environment & Version information
cider-nrepl version
latest
Operating system
Linux
The text was updated successfully, but these errors were encountered: