search

ignatov / intellij-erlang

Erlang IDE
https://www.jetbrains.com/help/idea/2018.2/getting-started-with-erlang.html
Other
735 stars 120 forks source link

Request for a feature: add an unresolved function to custom function definitions list #327

Open brigadier opened 11 years ago

brigadier commented 11 years ago

Functions from dynamically generated modules (compile:forms + code:load_binary) are marked as unresolved.

It would be nice to be able to right click on such function and mark them as resolved somehow, for the current project and current arity only.

ignatov commented 11 years ago

@brigadier Please specify the feature more precisely. At the moment compile:forms/1-2 and code:load_binary/3 loaded correctly in my setup atop of R15B01. image

brigadier commented 11 years ago

Yes, compile:forms + code:load_binary are loaded correctly. I'm talking about modules dynamically generated by code:load_binary()


{module, mymodule} = code:load_binary(mymodule, "mymodule", Bin), %%ok

%%everything is ok, we've just generated a module 'mymodule'
%% Now we call a function 'myfunction' from this module and it is marked as unresolved.
%%But what if just compiled mymodule exports this function? 
%%The plugin has no way to know this, so I'd like to be able to right-click on myfunction and 
%%choose "mark as resolved". Like, for example, spell checkers allow users 
%%to "add to dictionary" unknown words.
mymodule:myfunction(), %% unresolved
ignatov commented 11 years ago

@brigadier Got it. At the moment you can suppress the unresolved warning with a comment or via a special action: image But it'll suppress all unresolved issues for a whole function.