Hmmm. Don't know why those example use IgnitionGateway.get(). Modules are handed a module context during setup, and are expected to save it for anything like this. (Module context is a thin wrapper around a gateway context.)
The SDK doc refresh is being spearheaded by people with good intentions but the only involvement the dev team has is consultative / in review, AFAIK. It's not ideal, but we're all busy with 8.3 stuff
Got it, thanks for the replies. The tag writing function is in a separate class from the GatewayHook, but still in the gateway scope. Since the context is set in the GatewayHook class, is there a recommended way to pass it over to the class with the tag writing function?
You can make the GatewayContext available as a static/global variable in your hook, or you can pass it via constructor, or you can do whatever other thing you want. It's just a programming decision, not an Ignition SDK decision. Pretend you needed to make the choice in a scenario that didn't involve Ignition at all.
// This code example is Gateway scoped and assumes the `GatewayContext` object is available.
though it could be more clear that IgnitionGateway.get() is not how you actually get the context object, by passing GatewayContext as a param to the example function and truly leaving it as an exercise to the reader.
No, it is the name of the IA non-documented class that implements the gateway context interface for the whole gateway. You should not use it in any module code. Use the gateway context instance that your gateway hook is handed during startup.