Activate method does not work correctly about abap-adt-api HOT 5 CLOSED

I think I saw it when I firstly coded this in the editor plugin but got lost in the rewrite.
Will have to look into it.
Classes work ok AFAIK, perhaps they fail when trying to activate a single include.
Will look into it

from abap-adt-api.

In our case we tried to activate a single whole class, not an include. We used setObjectSource on the main class and the public include beforehand.

Everything worked, iff we used "$TMP" package and "Z" namespace. As we switched from "$TMP" to a real package with transport request, it didn't work anymore.

I think ADT checks the result of the first call and omits the second call on demand. Exactly the place where you set "success: false" should trigger the second call.

from abap-adt-api.

Weird, as I don't have that problem in the editor plugin, which I'm using regularly.
Anyway it should be in the API, no question about that.
From what I see in the Eclipse responses, the response is what I expect already, so it should only a matter of exposing the parameter

I just pushed a change that should allow you to pass this from the caller, only validate it didn't break existing tests but didn't test the new call, partly because I suspect getting a proper test case would be a bit of a pain. (BTW, if you can provide a reliable one I will include in my test suite)

Could you please try if this works as expected? If so I'll bump the npm version and release it

from abap-adt-api.

Perhaps it doesn't work for me, because I have much more recent versions of Netweaver than you :-).

Just release it. It looks good for me. I will test it tomorrow. It is more easy to test if I can just take the released version.

from abap-adt-api.

from abap-adt-api.