Feature: Add Symbol Table from Org to Scratch Org
Issue #1690
new
As the one of the upcoming features of package deployment is validation on install is it possible to add an additional OST to a scratch org from a sandbox or production org?
Comments (5)
-
repo owner
-
reporter
Hi Scott
sorry if that’s confusing. Let me elaborate.
From the release notes:
Can’t Untangle Your Metadata? Try Org-Dependent Unlocked Packages (Beta)
Org-dependent unlocked packages are a variation of unlocked packages that allow you to create packages that depend on unpackaged metadata in the installation org. You can use org-dependent unlocked packages when untangling your production org metadata is a daunting project. When you use org-dependent unlocked packages, metadata validation occurs during package installation, instead of during package version creation.
As such - being able to validate that metadata using an OST would be advantageous. So my suggestion is to add the OST from the installation org to the scratch org.
So yes - I want to have 2 OST’s for development against a scratch org for an Org-dependent unlocked package. One for the metadata in the package and one for the installation org so that we can kind of validate the ‘other’ metadata while developing an org dependent package.
Does that make sense now?
-
repo owner
Hey, just wanted to let you know that I'm not ignoring you. I'm trying to wrap up a small release for this week that was already pretty much complete. I'll take a closer look at this beginning of next week and let you know if I have any additional questions.
-
reporter
All good. No rush on this as it’s a beta thing anyway.
-
repo owner
- removed version
- changed component to Offline Symbol Table
- Log in to comment
I'm not sure that I follow. Are you wanting to have two OSTs, one from the scratch org and one produced from another org, or are you just wanting to be able to specify an alternative OST (temporarily?) produced from another org?