-
Notifications
You must be signed in to change notification settings - Fork 3
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
Composer package #28
Comments
Hey this is definitely a good idea. I will take it away and see what we can do. |
Hey are you using composer only or are you using a framework like Symfony as well? |
We're currently using composer as well. Our frameworks are proprietary. |
@aclarkd We are using a framework, but the intent is to take advantage of the wrapper in an internal package that we have that is not framework-specific. It handles how data is handed off to providers. |
Hey Andrew, just following up with you to see if there's any news on getting this as a composer package and into packagist? Thanks! |
Hey thanks for checking in. We are currently in development for a new version of our API which has updated auth and a newer JSON format for the leads. We do have plans to update the submitter to produce the new JSON format, use the new auth and add a version on composer. Right now we don't have an exact date for that though. With the new API we have added a couple of features for developers, the ability to assign to a sales person by name and the 201 from the API now returns the data that was stored in Lasso. |
Getting ready to upgrade to use this official api wrapper, however there is a bit of friction involved with the current process of having to independently manage this dependency. Are you considering getting this into a composer package with semantic versioning?
Thanks!
The text was updated successfully, but these errors were encountered: