-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
alias overrriding even with Elixir. prefix #12456
Comments
I think what's happening is:
I'm not sure what the right fix is, we need to be able to distinguish between the legit alias removal and the case where it is triggered by a nested defmodule. |
@sabiwara I would argue that we should not do an alias if the module starts with Do you agree @lukaszsamson? |
It sounds reasonable. @josevalim when we are at it let's take a look on another non trivial example. Does this behave correctly? It seems
|
@lukaszsamson it is correct to me, because |
* fix warnings * get line in predictable way * position is :erl.anno since 1.16 * alias external submodule behaviour changed in 1.16 see elixir-lang/elixir#12456 * fix parser tests this is a WIP solution atm * handle anonymous_call in complete * fix version check and another test * remove not needed test * pass cursor line to parser fall back to container_cursor_to_quoted if unable to parse * fix crash in parser * fix warning * improve parser * return correct error on parse success via container_cursor_to_quoted * do not fall back to container_cursor_to_quoted when fixing no env * format on 1.15 * fix some dialyzer errors
I wanted to see how this alias overwriting work in case of external submodules and I've found something odd
So it removes the alias. This does not happen for nested external submodule e.g.
Elixir.Child.One
Originally posted by @lukaszsamson in #12451 (comment)
The text was updated successfully, but these errors were encountered: