Context
During the review of PR #1843, the team discussed whether PackageInstance and PackageTestConfig should remain separate classes.
After discussion, the consensus is to merge them into a single class. The rationale:
- The separation adds an additional layer of abstraction without clear concrete benefits at this stage
- Even with more attributes in a merged class, we can use grouping and docstrings to maintain clarity
PackageInstance tracks intermediate states/artifacts while PackageTestConfig supplies input configs, but these purposes can coexist in one class
References
Context
During the review of PR #1843, the team discussed whether
PackageInstanceandPackageTestConfigshould remain separate classes.After discussion, the consensus is to merge them into a single class. The rationale:
PackageInstancetracks intermediate states/artifacts whilePackageTestConfigsupplies input configs, but these purposes can coexist in one classReferences