Panic on list when current page is nil

[jjcollinge]

$ azbrowse version
2.0.155234515
fe9e55f
2020-07-02T10:42:05Z
go version go1.14.4 linux/amd64
linux/amd64

I've just tried launching azbrowse and hit this panic caused by this line. Looks like we're checking if currentPage != nil for earlier operations but not before trying to access the ExpandedNodeItem property. I've not had time to understand the bigger context yet - A few open questions (I'll answer myself when I get time but feel free to shortcut me):

• Why would currentPage be nil?
• What should be the behaviour when it is nil`?
  

[lawrencegripper]

Oooh interesting - thanks for raising this one. I'll have a rummage.