Thanks for confirming. My point is that there is an AL:Package command in VS Code. I don't like mixing up command names. It's either package or compile. And in this case package is the correct term. Call me purist or perfectionist (which I am actually), but I'm a bit of a stickler for accuracy.

In fact this is packaging, right? Compiling means translating into another language.

That's easy, the Rest Client module supports mocking test results. You don't need to use the new HttpClientHandler feature in test codeunits for this, it's a built-in feature of the Rest Client itself.

I had this idea for my session at Directions NA! Great minds... 😊

I'm also using it daily. But I can't get used to how the Tab key works with auto completion. When a dropdown is open, then I expect Tab to insert the selected value rather than a suggestion. I can't find a setting for this. Using Enter for dropdowns and Tab for suggestions is very uncomfortable.

The Rest Client is my favorite. 😊

I have solved this in the past with a local web service and Azure Relay Hybrid Connection. Works like a charm.

Thanks, and yes, alguidelines.dev is part of my source to pick ideas from.
I may mention LinterCop. But the focus is on real knowledge. Tools are most useful when you understand what they do and why they do it.

The typical use case is transferring data from a buffer table without code in the triggers to the target table. For example a buffer table filled by an API call.

HttpContent.ReadAsStream (in .Net) copies content into a memorystream (buffered in memory). That's why you can still read the stream while the original HttpContent is already out of scope.
In my opinion this is a hack. I'd rather have a solution that works with properly scoping the variables.

Codeunit 2351 "Rest Client Impl." implements a few Create() and Initialize() functions to assign default implementations to interfaces in case none were provided.
All public functions call CheckInitialized() to enforce the codeunit is initialized.
A real constructor like C# classes would be welcome!

No, that's my point. Of course it makes sense placing triggers in the correct order. But with nested dataitems the triggers of the outer dataitem come after the inner dataitem. Which makes it less readable.

Now do the same with nested dataitems so that the order of triggers in outer and inner dataitems make sense. 🫣🙃

You should look at the Rest Client module. Much easier to work with!