Comments (11)
Hi Mark,
Can you provide more detail about what you're working on? TeleSign encourages you to use the latest SDKs as they're all up to date. Without much info, some things I can think of that might address your situation:
- If you're doing a free trial or you are a customer but not an Enterprise customer), you will want the latest PHP SDK (so the 2.0.0 tag) because that contains all TeleSign's new product offerings.
- If you want to use Enterprise products the latest PHP SDK is in a private repository. If you're already a customer you can ask your TAM for access. If you are new, then write to [email protected] for help getting access.
-Erikka
from php_telesign.
Hi Erikka,
Thank you for the response. We have some legacy code we are working with that was manually including the v1.0.0 code. We want to use Composer in our workflow to handle our 3rd-party libraries, but Telesign v1.0.0 is unable to be installed using Composer.
Updating to the latest version sounds like a prudent thing to do, but as a first step we'd like to get the existing code to work via Composer before changing versions.
Would it be possible to draft a release for the existing v1.0.0 tag and refresh Packagist so the version becomes available to Composer?
Thanks.
from php_telesign.
I sent a note asking the team about this - we are heading into the weekend so I will check again with them on Monday.
from php_telesign.
Hi Mark,
You can "inline package definition" in your legacy project's composer.json, like this, https://gist.github.com/luka-zitnik/735e5b3b001cd6dafbe2684559011faf
This is not an official statement from TeleSign, but only my own remark.
from php_telesign.
Hi Luka,
We are currently doing it that way, with a custom repository definition. But, it seems like a hack a bit.
Hopefully TeleSign can publish the existing v1.0.0 git tag as a release?
from php_telesign.
Hi Kristopher,
I have the patch in a fork, but still don't have the approval.
from php_telesign.
https://github.com/TeleSign/php_telesign/tree/v1.1.0
from php_telesign.
Thanks!
from php_telesign.
Should have used classpath instead of files. Let me know if that's an issue to you.
from php_telesign.
Hi, classmap would be a little nicer, but I think the performance impact of using "files" won't be noticed.
Thanks,
from php_telesign.
I'll leave it then. Thank you.
from php_telesign.
Related Issues (6)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from php_telesign.