Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove dependency from NPSP, see if it can stand alone as a package #9

Open
mattmartin26 opened this issue Feb 2, 2021 · 1 comment
Assignees

Comments

@mattmartin26
Copy link
Member

mattmartin26 commented Feb 2, 2021

Chancery package would most likely be installed into Customer NPSP orgs but if its not necessary to make a hard dependency then there are a few advantage:

  • Would improve time for spinning up Dev orgs
  • Would reduce number of exceptions during update_dependencies flow

Possibilities:

  • Only make it dependent on the Affiliations object...? Not on the entire NPSP package.
@mattmartin26 mattmartin26 self-assigned this Feb 2, 2021
@mattmartin26
Copy link
Member Author

So far so good - able to spin up scratch orgs WAY more quickly now.

Have yet to test the impact when creating a Managed Package & deploying to new org.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant