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) »
  • The API stands and falls together
Pages: 1 [2]

Author Topic: The API stands and falls together  (Read 2965 times)

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: The API stands and falls together
April 25, 2012, 12:32:38 am
NB - the main reason I want to add 'pseudoconstant' is that I want to push that instruction down to the xml level so the information about how to access the pseudoconstant is not added at the _get_spec level or _create_spec level - as it's generic to both, & it seems generally useful to have it defined at the $dao->fields level
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 [2]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Developer Discussion »
  • APIs and Hooks (Moderator: Donald Lobo) »
  • The API stands and falls together

This forum was archived on 2017-11-26.