"go to definition" and the library list

[BrianGarland]

Over a year ago there was some discussion about making "go to definition" work with the library list. It works as long as the definition is in the same source member but if it is based on a /include then you're out of luck.

I haven't had the need for this until recently and it doesn't seem to be implemented yet. Any idea where this fits on the roadmap?

[worksofliam]

/include and /copy resolution absolutely supports the library list now.

Hovering over the /copy or /include statement should show where the file was resolved from.

[BrianGarland]

But the F12 from a procedure call doesn't bring you to that source. You don't want to have open every /include to get there.

[worksofliam]

Are you suggesting that hovering shows the correct location, by F12 (go to definition) does not take you to the right place?

[BrianGarland]

My initial question as about F12 (go to definition) so I was trying to redirect to that topic.

After you mentioned hovering I tried that and get "not found" even though it is in the library list.

[BrianGarland]

It works if it is in the current library, but not if it is in a library in the user library list.

[worksofliam]

I checked to confirm and it works for me.

I would check out the output logs and perhaps share them here if it does not work for you.

[BrianGarland]

/home/BRIAN: for f in /QSYS.LIB/EMPBJG.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/ZWBRIAN_18.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/ZPBEV__18S.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/ZPBEV__17S.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/ZPBEV__16S.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/VVIPEYE.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/VIPDEVELOP.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/TECHCOMMON.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/VGPL.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/QGPL.LIB/QRPGSRC.FILE/INCLUDE1.MBR /QSYS.LIB/QTEMP.LIB/QRPGSRC.FILE/INCLUDE1.MBR; do if [ -f $f ]; then echo $f; break; fi; done
{
    "code": 0,
    "signal": null,
    "stdout": "",
    "stderr": ""
}

I think I see the problem. In the log it is not referencing the iASP in those path statements. All the libraries except EMPBJG are in an iASP.

[worksofliam]

@BrianGarland Did you fill out in the ASP option in the connection settings? I am hoping we will fix that one with a PR soon. (#2339)

[BrianGarland]

Ah, that was it.

I had the ASP there at one time but removed it after some fixes to MDCMS eliminated the need for it in their extension because my *JOBD specifies the ASP.

[worksofliam]

Nice. You won't have to do this in the future and we will instead grab the ASP from the user profile.