You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest release (to be honest, I only noticed in the latest release)
I saw that "objectscript.export.noStorage": "true" is no longer an option in the extension.
Is there an alternative?
I have here a question from my Architect about the side effect:
What do you think this will do for the Schema changes when you are working classes with existing data (Lots of it)
What we find now is that when we compile classes, the storage information generates a lot of metadata that may not be needed for our cases.
If you require more information I will gladly provide it.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hi @JulianWolfDXC, this setting was removed as part of an overhaul of the client-side editing workflow. I first announced this back in August on the Developer Community, which is linked to the original Pull Request #1401. The reason for removing this setting is that Storage is an integral part of the class definition like any other class member and it should be source controlled. Can you give me an example of the specific Storage data that you don't want to export/source control?
Hi All
With the latest release (to be honest, I only noticed in the latest release)
I saw that
"objectscript.export.noStorage": "true"
is no longer an option in the extension.Is there an alternative?
I have here a question from my Architect about the side effect:
What we find now is that when we compile classes, the storage information generates a lot of metadata that may not be needed for our cases.
If you require more information I will gladly provide it.
Thanks in advance.
The text was updated successfully, but these errors were encountered: