Thanks @Joel Solon!

But all this could be achieved without instance methods, right? Anyway, I'm struggling to find an easy way to debug a failed unittest. @Michael Davidovich suggested the closest way to achieve it but I still want to find something really handy, e.g. an additional "clickable button" in VSCode above the test method that invites "debug this test method". Similar what we have for class methods now - debug this classmethod and copy invocation.

That'd be ideal.
 

Package Manager is going to be a part of a product in near future, but right now it is not a part and can be installed with the following command:

s r=##class(%Net.HttpRequest).%New(),r.Server="pm.community.intersystems.com",r.SSLConfiguration="ISC.FeatureTracker.SSL.Config" d r.Get("/packages/zpm/latest/installer"),$system.OBJ.LoadStream(r.HttpResponse.Data,"c")

Caution!  This is for IRIS only.

The package manager.

It has documentation, a bunch of videos, and there is a tag here.

Hi @Guillaume Rongier !

Well explained. I just hope the UI be more intuitive - this pays a lot in the future for the better adoption of the tool.

I understand that there are not many letters in the alphabet and it can go to the end quickly. In this case I'd keep with what you think on one-letters and also introduce synonyms of fulltext with double --.e.g.

--import for import,

--export for export and 

--status for status.

This could help with readability in long scripts with cli or with documentation.