You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifically this is discussing the behavior of cljr--js-alias-p, which ignores a magic require alias prefix "js" if and only if it's in a cljs file. It will attempt to lookup the namespace in a cljc file. It's less clear what the behavior is inside of a #?(:clj) or #?(:cljs) language context within a cljc file, but I would expect that it should use the cljs behavior inside of a cljs context in a cljc file.
Expected behavior is that js/ in a cljs context should ignore the magic alias lookup for both cljs and cljc files.
The text was updated successfully, but these errors were encountered:
I can take a look, I agree it should be pretty easy at this point. That said, I'm pretty low capacity for the next month or two, so no promises on when.
vemv
added a commit
to zenmacs/clj-refactor.el
that referenced
this issue
Jul 31, 2023
Context: #522 (comment)
Specifically this is discussing the behavior of
cljr--js-alias-p
, which ignores a magic require alias prefix "js" if and only if it's in a cljs file. It will attempt to lookup the namespace in acljc
file. It's less clear what the behavior is inside of a#?(:clj)
or#?(:cljs)
language context within a cljc file, but I would expect that it should use the cljs behavior inside of a cljs context in a cljc file.Expected behavior is that
js/
in a cljs context should ignore the magic alias lookup for both cljs and cljc files.The text was updated successfully, but these errors were encountered: