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
{{ message }}
This repository has been archived by the owner on May 16, 2019. It is now read-only.
Ok so this is an example of one of the biggest pitfalls of the ide version versus the flow cli. In this example, it is reporting to me that someone is calling the function without the "title" and "label" values.
However, it is not telling me ANY information about where or who is doing this. It could be any function in my program (I believe within an open tab? but still). I then need to search around trying to find it.
It says "see also: function call" - which is the first step in the trace but is actually not helpful at all. I have traces setup to a level of 3 so I was hoping it would at least give a little summary or something that would tell me the actually caller.
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up. The problem here is that the LSP has no support for 'traces' at the moment (RFC: microsoft/language-server-protocol#260) so we'll have to be a bit creative here.
I guess the least we can do is show the filename here, even if it's not clickable.
Ok so this is an example of one of the biggest pitfalls of the ide version versus the flow cli. In this example, it is reporting to me that someone is calling the function without the "title" and "label" values.
However, it is not telling me ANY information about where or who is doing this. It could be any function in my program (I believe within an open tab? but still). I then need to search around trying to find it.
It says "see also: function call" - which is the first step in the trace but is actually not helpful at all. I have traces setup to a level of 3 so I was hoping it would at least give a little summary or something that would tell me the actually caller.
The text was updated successfully, but these errors were encountered: