At some point since I posted the comment linked to above the rules got even more complicated. See https://docs.intersystems.com/iris20241/csp/docbook/DocBook.UI.Page.cls?... from the 2024.1 doc which states that "Some system default settings can override the corresponding production ... values" (my bolding).

That doc section names two settings but doesn't claim to be a comprehensive list 😾

Please also see https://community.intersystems.com/post/system-default-settings-versus-p... to try and understand how easy it is for a system-specific setting to get overridden by a setting added to the XData block of the prodclass. Then, if you're not super-careful about how you transfer the prodclass between environments you can inadvertently end up with the live production talking to the test interfaces.

These Code Actions are contributed by the InterSystems Language Server extension. To request improvements please open issues at https://github.com/intersystems/language-server/issues

The presence of the VS Code lightbulb is controllable with the editor.lightbulb.enabled setting, which can be set per-language if you wish.

For example, in Settings Editor use this filter to alter the setting at user-level or workspace-level only for ObjectScript classes.

@lang:objectscript-class editor.lightbulb.enabled

Are you using the client-side editing paradigm, where the files on your VS Code workstation are managed with, say, Git, and imported to an IRIS server for execution? Or are you using the server-side editing paradigm, which is equivalent to the IRIS Studio way of working?

Also, please explain why you don't want the storage information in the class file.