search

blak3r / freshdesk-solutions

Includes wrapper class for implementing freshdesk rest api methods related to "Solutions". Also includes some curl examples.
7 stars 11 forks source link

Ticket support? #1

Open CostaC opened 11 years ago

CostaC commented 11 years ago

Hi, looking great so far. :) Any plans to support Tickets ?

blak3r commented 11 years ago

I wasn't. I think there are several other projects on github that do that already.

Should be pretty easy to extend my class though... Happily will pull in changes to add additional methods.

~blake

On May 18, 2013, at 9:34 PM, Costa notifications@github.com wrote:

Hi, looking great so far. :) Any plans to support Tickets ?

— Reply to this email directly or view it on GitHub.

EVODelavega commented 10 years ago

@CostaC: I'm currently working on a composer-aware fork of this repo that supports tickets (https://github.com/EVODelavega/freshdesk-rest/tree/feature/composer), if you're still looking for a wrapper, help yourself

@blak3r If you want, I'd also be happy to send a pull request to a new branch

blak3r commented 10 years ago

Sure. Happy to pull it in. Thanks!

Sent via mobile

On Jul 7, 2014, at 11:11 AM, EVODelavega notifications@github.com wrote:

@CostaC: I'm currently working on a composer-aware fork of this repo that supports tickets (https://github.com/EVODelavega/activecampaign-api-php), if you're still looking for a wrapper, help yourself

@blak3r If you want, I'd also be happy to send a pull request to a new branch

— Reply to this email directly or view it on GitHub.

EVODelavega commented 10 years ago

@blak3r Cool, I'll let you know when I'm done testing (the composer update/install hooks are untested at the moment). Pulling my composer-aware branch will result in a merge-conflict, though, so perhaps it might be best to create a branch, set to some common ancestor or something

blak3r commented 10 years ago

I take it you forked an old copy of my repo? I haven't ever made any major changes should be easy to merge in. But perhaps what your creating should be it's own project that depends on my project?

I'm not exactly sure what the composer and stuff have to do with rest API.

Sent via mobile

On Jul 7, 2014, at 11:21 AM, EVODelavega notifications@github.com wrote:

@blak3r Cool, I'll let you know when I'm done testing (the composer update/install hooks are untested at the moment). Pulling my composer-aware branch will result in a merge-conflict, though, so perhaps it might be best to create a branch, set to some common ancestor or something

— Reply to this email directly or view it on GitHub.

EVODelavega commented 10 years ago

I forked a fork of your repo, so merging the master is still possible, but I'm mainly working on the composer-aware branch, which can't really be merged into your master branch (as it no longer uses the FreshdeskRest class as such). The composer stuff was added so I could include this wrapper in a project that uses the composer.phar dependency manager, so it can be added to Zend or Symfony2 projects. I'm going to add some more methods to create, update and manage tickets, too, which is why I commented here. I just noticed that this was an older issue, though