Improve httpRegion dependency tracking

[fredrikhr]

A non-global httpRegion should implicitly be dependent on the global regions of the file.

Since global regions are always executed when @import-ing or directly executing a region in a file, it is not helpful to invalidate their dependents when global regions are executed. Since a global region cannot be @ref-ed in itself that is okay.

Having the dependency tracking on the context is not ideal: the context is recreated every time the httpyac-CLI or VS Code execute a region or file. Instead dependency tracking should really be a feature of the region itself.

This makes the context argument for the registerRegionDependent and resetDependentRegions functions obsolete. I kept the argument (and retyped it to any) to keep backwards compatibility.

[fredrikhr]

Hmm, so i tested this successfully in CLI, but in VS Code this does not work for some reason. One thing though: the new property breaks the debug tree view in VS Code because of circular object graphs (regions depend on global regions which are in the same file and thus in the same tree)

[AnWeber]

@fredrikhr debug tree view is not really important. I wanted to be able to understand the internal state of my extension even without debugging (at work). But I don't think that's a major problem either, since only the current level is ever queried, right?

There may also still be an overlap between changes from us, as #243 affects the exact same code locations. I am currently considering if and how I can possibly adjust the loopMetaDataHandler so that it integrates better into the normal flow. And doesn't need any special solutions. It has code from createRequestInterceptor, httpRegionUtils (with some code missing => #242) and now your dependency tracking :-(

if (!next.done) {
  utils.report(context, `${next.value.index} loop pass`);
  Object.assign(context.variables, next.value.variables);
  await utils.logResponse(context.httpRegion.response, context);
  context.httpRegion = this.createHttpRegionClone(context.httpRegion, next.value.index);
  if (this.request) {
    context.request = cloneDeep(this.request);
  }
  hookContext.index = this.index;
}

[fredrikhr]

Ah, I found the reason why this did not work in VS Code. Previously there was a conditional in processHttpRegionActions which checked for both context.processedRegions and whether the region was global or not. My dependency tracking only cares about the latter.

But then I needed to rebase onto main and the conditional has been removed, so I now only added the check for global regions accordingly.

This now works both in CLI and VS Code.

[AnWeber]

Sorry, I had to change the logic of loopMetaDataHandler as announced. Could you please check the conflicts and test your changes again. I think your change in the loopMetaDataHandler is no longer needed. Thanks.

[fredrikhr]

@AnWeber rebased and tests showing green 👍
I have actually compiled a local vscode-extension vsix that I have been running on my machine in the last days... So far the dep-tracking seems to work great... By we should take a look at the Debug tree view in the vscode extension.

[AnWeber]

thx:-)