Allow renaming a package #379
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Right now the only way to "rename" a package is to delete it and recreate with the correct name - make it easier.
|
👍 |
|
If anything the rename should happen in composer.json first. |
|
I'm not sure what that comment means @Seldaek (in terms of what is required for something to get done). Guess this problem will just sit until someone else picks up the ball then - 😞 |
|
I just mean that you shouldn't be able to rename things on packagist, you should rename it in the composer.json (and possibly we should enforce that you replace the old name too, but not sure about that) and then tell packagist "yo I renamed this, please update the name". |
|
That sounds like a validation rule - but I'm not intimate enough with the code to understand how you'd want that to be written. |
|
Closing due to lack of interest/guidance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It aught to be rare, but there are times when renaming a package is desirable - such as when an author manages to use someone elses namespace; make it possible to rename a package without deleting and recreating the package.
A follow up to this could be to track renames and automatically handle/redirect requests for the renamed repository - though that's a bit more involved and not something I wish to implement at this time (IMO the way the search handles requests for missing packages is not perfect, though sufficient).
This resolves #47 and would help alleviate #163