Skip to content

Support for config.subsplit-publish.json #1

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

Open
alexander-schranz opened this issue Feb 28, 2024 · 4 comments
Open

Support for config.subsplit-publish.json #1

alexander-schranz opened this issue Feb 28, 2024 · 4 comments

Comments

@alexander-schranz
Copy link

Description

My root composer.json does not require to know anything about the repositories. It would be nice that "repositories" is not required and the supports the config.subsplit-publish.json file used by https://github.com/frankdejonge/use-subsplit-publish.

Example

https://github.com/schranz-search/schranz-search/blob/0.3/config.subsplit-publish.json

@soyuka
Copy link
Owner

soyuka commented Feb 28, 2024

that's nice thanks will look into it, so according to how I do things, repositories would be added reading [config.subsplit-publish.json](https://github.com/schranz-search/schranz-search/blob/0.3/config.subsplit-publish.json) ?

@soyuka
Copy link
Owner

soyuka commented Feb 29, 2024

I'm not fond of this as I don't have the composer package names in that file. Instead, what about generating that config.subsplit-publish.json from the composer.json files? I think that all the information that are inside the config.subsplit-publish.json could be inside each of the composer.json (like the actual git repository).

@alexander-schranz
Copy link
Author

alexander-schranz commented Feb 29, 2024

I'm not fond of this as I don't have the composer package names in that file.

You can get the package name the same way as for the repositories configuration of composer while you have there the path you have here directory configuration of the config.subsplit-publish.json and can read then directory + /composer.json. I don't think that it is required to generate here out of composer.json config.subsplit-publish.json.

@soyuka
Copy link
Owner

soyuka commented Feb 29, 2024

yes but right now I'm not reading the composer.json files myself as I want to leave that out to composer

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

2 participants