CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion »
  • APIs and Hooks (Moderator: Donald Lobo) »
  • What could be improved in the API
Pages: [1]

Author Topic: What could be improved in the API  (Read 960 times)

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
What could be improved in the API
March 26, 2011, 11:40:55 am
This is not intended to be done on 3.4/4 but as every civicrm_api3 is called from civicrm_api, we can put a try catch block wiithin civicrm_api and get rid of all the try catch within each civicrm_api3

Beside taking out loads of lines of code, this would allow a more elaborate error processing (eg dealing differently with a pear exception about sql error, having our own custom exceptions...

X+
-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: What could be improved in the API
March 26, 2011, 11:54:37 am
I think that makes sense
Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion »
  • APIs and Hooks (Moderator: Donald Lobo) »
  • What could be improved in the API

This forum was archived on 2017-11-26.