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) »
  • REST params change suggestion
Pages: [1]

Author Topic: REST params change suggestion  (Read 571 times)

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
REST params change suggestion
January 08, 2011, 12:44:35 am
1) I already added debug, so &json=1&debug=1 formats the json so that's more human readable (add newlines and tabulation)

2) I'd want to add a new return=sort_name,first_name...

would work exactly the same as return['sortname']=1&return['first_name']=1 ... but much shorter (pet issue of mine, that's already how it works on the {crmAPI} and I find it friendlier to read and type).

What do you think ? (obviously, we keep the return[attribute]=1 too)

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: REST params change suggestion
January 08, 2011, 11:59:59 am
Assume this only affects REST - does make 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) »
  • REST params change suggestion

This forum was archived on 2017-11-26.