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

Create sfdx-package.json #1915

Closed
AllanOricil opened this issue Feb 5, 2023 · 5 comments
Closed

Create sfdx-package.json #1915

AllanOricil opened this issue Feb 5, 2023 · 5 comments
Labels
feature Issue or pull request for a new feature

Comments

@AllanOricil
Copy link

AllanOricil commented Feb 5, 2023

Is your feature request related to a problem? Please describe.

No, it isn't.

What are you trying to do

I want to find package configurations in a file in the root of the package, not in sfdx-project.json. It would work like package.json or pom.xml, like seen in node and maven projects. The sfdx-project.json would become an aggregator of packages. It can contain 1 or many sfdx packages, and it would also behave like a parent sfdx-package.json.

Describe the solution you'd like

A sfdx-package.json must xist in the root of every package. All the information that is specific for a package, which is currently located in the sfdx-project.json, must be moved to this file.

{
  "name" : "bla",
  "version": "1.0.0",
  "description": "bla",
  "repository": "https://githu.com/bla/bla",
  "type": "unlocked",
  "is_org_dependent": false,
   "dependencies": {
       "d_1": "1.0.0", // dependencies from the devhub
       "d_2": "https://github.com/bla/[email protected]", //non packaged dependency from a repository
       "d_3": ./d_3 //maybe it is a directory dependency that isn't packaged.
       "d_4": //managed packages could also be here. For instance, "vlocity" packages could be necessary for me to start working on changes to my package
    },
    "sfdx_plugins":{
          "sfdx-git-delta": "^5.14.0"
     },
    "scratch_org_config": "./bla-so.config" //file path, including github paths because there could exist a common file shared by many packages from different sfdx projects, or it could be inline if someone needs it
   "key_store": //customers can use their own, or salesforce could sell this as a service.
   "key_id": //ID to locate key within a key store. If passed sfdx will fetch the key automatically at runime and won't save it anywhere. This also means the package must be created/installed using a key. 
    ...

    //string replacement feature properties
    ... 
   //permission set feature properties
    ...

  //any other attribute that is used for the lifecycle of a package
}

Describe alternatives you've considered
Couldn't find one

@AllanOricil AllanOricil added the feature Issue or pull request for a new feature label Feb 5, 2023
@github-actions
Copy link

github-actions bot commented Feb 5, 2023

Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments.

@git2gus
Copy link

git2gus bot commented Feb 5, 2023

This issue has been linked to a new work item: W-12493297

@AllanOricil
Copy link
Author

#1950

@dieffrei
Copy link

+1

@AllanOricil AllanOricil closed this as not planned Won't fix, can't repro, duplicate, stale Mar 3, 2023
@AllanOricil AllanOricil reopened this Mar 4, 2023
@AllanOricil
Copy link
Author

This could also be called sf-package.json, since now you have rename sfdx to sf. And sfdx-project.json could become sf-project.json

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Issue or pull request for a new feature
Projects
None yet
Development

No branches or pull requests

2 participants