Skip to content
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.

Analyze Dependency for Packages #764

Closed
azlam-abdulsalam opened this issue Nov 18, 2021 · 0 comments · Fixed by #771
Closed

Analyze Dependency for Packages #764

azlam-abdulsalam opened this issue Nov 18, 2021 · 0 comments · Fixed by #771
Assignees
@aly76
Labels
new feature new feature
Milestone
Release - Decembe...

Comments

@azlam-abdulsalam
Copy link
Contributor

During validate, packages can have accidental dependency in the opposite direction which is only uncovered during build or not uncovered at all for source packages. If this information can be shifted to pull request, it would prevent refactoring that needs to be done with an incorrect PR that is merged
@azlam-abdulsalam azlam-abdulsalam added the new feature new feature label Nov 18, 2021
@aly76 aly76 mentioned this issue Nov 26, 2021
Merged
azlam-abdulsalam pushed a commit that referenced this issue Nov 30, 2021
@aly76
Validate dependencies as part of orchestrator:validate command (#771)
d523919 
- Validate dependencies as part of orchestrator:validate command
- Check for misordered dependencies
- Check for missing dependencies for unlocked packages
- Update to latest version of sfdc-soup dependency
- Fix bug causing MDAPI deployment reports to not write to file, and impact analysis to fail
- Closes #764
@azlam-abdulsalam azlam-abdulsalam mentioned this issue Feb 23, 2022
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@aly76 aly76

Labels
new feature new feature
Projects
None yet
Milestone
Release - December 2021
Development

Successfully merging a pull request may close this issue.

Validate dependencies as part of orchestrator:validate command dxatscale/sfpowerscripts
2 participants
@aly76 @azlam-abdulsalam