Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Just asking for a bit more documentation. So far I think it's limited to a README file with "Drupal module making it possible to expose Views from Views.module through Service.module's API:s"
Comments
Comment #1
frazras CreditAttribution: frazras commentedIm not sure how to write "official documentation" but the general way this module operates is as such:
Comment #2
mgiffordAdding that to the README file would be a good start. There's often a way for families of modules to do documentation that is consistent enough. Search does a reasonable job - http://drupal.org/project/services_search
there's also http://drupal.org/documentation/modules/services
All this stuff helps get folks started. Possible examples are often cool too. Especially based off of default Views..
Comment #3
jefflinwood CreditAttribution: jefflinwood commentedThere isn't any documentation for Services_Views - I'd be happy to help with this, here is a brief outline of what I would put into it
* What it does
* Prerequisites
* Configuring with an endpoint
* Basic Usage
* Arguments and Parameters to Views (limit, offset, args, display_id)
Does someone have a quick example of arguments and parameters that works using the REST Server and Services_Views?
Comment #4
Alex Andrascu CreditAttribution: Alex Andrascu commentedVery interested in #3 aswell
Comment #5
7wonders CreditAttribution: 7wonders commentedI havent had any need for passing in filters so if anyone knows how, please add.
Comment #6
7wonders CreditAttribution: 7wonders commentedComment #7
mototribe CreditAttribution: mototribe commentedgreat documentation, thank you!!!
Shouldn't the urls end in view_name.json instead of view_name ?
Comment #8
7wonders CreditAttribution: 7wonders commentedJust view_name seems to work fine for me.
Comment #9
kerberos CreditAttribution: kerberos commented.json is only needed it you want a JSON response. Many other formats are possible (depending on your server settings) and the default is XML if there is no extension. Alternatively you can specify the format through the request rather than the URL.
-Daniel
Dragonvale Breeding Guide
Comment #10
kylebrowning CreditAttribution: kylebrowning commentedDont forget you can pass Accept: application/json headers as well, if you dont want to sue the extension
Comment #11
kerberos CreditAttribution: kerberos commentedI just edit my answer to include that and then I saw your post. Sorry. :)
-Daniel
Comment #12
Jānis Bebrītis CreditAttribution: Jānis Bebrītis commentedin addition to #5
Comment #13
7wonders CreditAttribution: 7wonders commentedAdded Janis' feedback to the above post so its easier to copy paste when its added as a readme.txt.
Comment #14
ygerasimov CreditAttribution: ygerasimov commentedI have updated documentation. Both project page and README file. Should you have any questions please open new issues.
Comment #15
tinflute CreditAttribution: tinflute commentedthis documentation has not yet made it into the 6.x README
Comment #17
Jānis Bebrītis CreditAttribution: Jānis Bebrītis commentedCan you add this to 6x branch too, please?
Comment #18
ygerasimov CreditAttribution: ygerasimov commentedJanis, I am not quite in position to maintain 6.x branch. I would really appreciate if you can advise what text for documentation I should place for 6.x branch so I will commit it. Thank you.
Comment #19
tinflute CreditAttribution: tinflute commentedThe readme for 6.x should contain quoted text from #5 and #12 above, cut and paste.
Comment #20
ygerasimov CreditAttribution: ygerasimov commentedFixed. Thank you.