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

Change vendor name to something different than "Tx" #15

Open
mediaessenz opened this issue Jan 25, 2017 · 3 comments
Open

Change vendor name to something different than "Tx" #15

mediaessenz opened this issue Jan 25, 2017 · 3 comments

Comments

@mediaessenz
Copy link
Contributor

To avoid possible conflict with other extensions, please change vendor name to something different than "Tx".

@astehlik
Copy link
Owner

astehlik commented Feb 1, 2017

Thank you for taking the time for creating this issue.

Do you currently experience namespace conflicts? The Extension name is always unique. Therefore the second part of the namespace is always unique, no matter what the prefix is. Even if everybody would use the Tx prefix it should not matter because no extension key can be registered twice.

@mediaessenz
Copy link
Contributor Author

But we don't live only in the typo3 world. One reason why typo3 is going to use composer is to open up the system more to the PHP community. And this not only in one way.
So if someone wants to use your code inside another project than typo3, "Tx/Tinyurls" is not unique anymore.
The vendor name has also the function to show the users, where the code comes from. As long your company/username is not "Tx" its not the case.
And I already heard, that in future versions of typo3 (9 or 10), when the compose integration will be finished, the Extkey will be changed against "Vendor/PackageName".
Beside of all, a vendor name could also be a kind of advertising ;-)

@astehlik
Copy link
Owner

astehlik commented Feb 1, 2017

These are really good points you are making :)

I'll see how I can change this without breaking too much.

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