Proper package publishing #44
Replies: 5 comments
-
UPD So, I made a little research and find out that installation instruction will work properly only when repo section is added to
without that it will use original package (due to old namespace |
Beta Was this translation helpful? Give feedback.
-
UPD2 but anyway with this method there's still some issues with namespaces/classnames -- it cannot find any class from Tighten\SolanaPhpSdk in runtime :-( |
Beta Was this translation helpful? Give feedback.
-
UPD3 just checked other repo and seems when targeting exact version in composer it is working: "tightenco/solana-php-sdk": "^0.3.2" |
Beta Was this translation helpful? Give feedback.
-
UPD4! in previous config there's some autoload issues, so even tho it's installed by composer, then package namespaces and classes not available in the project, so seems proper config is to have repo in composer like this:
and target latest version:
|
Beta Was this translation helpful? Give feedback.
-
Hi @ComradePashka, thanks for the updates, yes we are still working on migrating to the new namespace and publishing a new release on packagist. |
Beta Was this translation helpful? Give feedback.
-
Hello!
I decided to use this package in my project, so I followed instruction but seems that
tightenco/solana-php-sdk
in fact is abandoned and there is noverze-app/solana-php-sdk
at packagist.orgThis a bit confusing. Does it mean that with
composer require tightenco/solana-php-sdk
we actually never use THIS repo?Should it be fixed? Should
verze-app/solana-php-sdk
be registered package at packagist.org and be suggested replacement for the former original package? Or at least should installation instruction be fixed to target this repo instead of former one?Thank you in advance,
cheers!
P.S. idk if package name is already somehow automatically target this repo, so post here instead of creating issue.
Beta Was this translation helpful? Give feedback.
All reactions