Difference between revisions of "2014-02-12 Telephone Conference DEVROOM / stepping stone GmbH"
From stoney cloud
| [unchecked revision] | [unchecked revision] |
(→Transcript) |
(→Transcript) |
||
| Line 72: | Line 72: | ||
| width="40px" | 1 | | width="40px" | 1 | ||
| − | | width="800px" | | + | | width="800px" | The REST API defines the following line as a return value. This is required and will not change. |
| + | * "location": "https://api.example.com/v1/resellers/4000001/customers" | ||
| + | You are correct in the assumption, that the following line will return the same information: | ||
| + | * https://api.example.com/v1/customers?belongsToResellerUID=4000001 | ||
| + | [[stoney_core:_REST_API#Filtering.2C_sorting_and_searching | Filtering, sorting and searching]] allows for the above query. | ||
| + | |||
| width="70px" | Info | | width="70px" | Info | ||
| width="70px" | All | | width="70px" | All | ||
Revision as of 10:37, 12 February 2014
Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH
| Location | Skype |
| Date | Wednesday, the 12th of Feburary 2014 |
| Time | 11:30 until 12:00 |
| Participants |
|
| Non participants |
|
| Agenda |
Open Questions:
|
Transcript
| No. | Text | What? | Who? | When? |
|---|---|---|---|---|
| 1 | In principal, the REST API should know the scope of variables. For example: billingAddress should be able to contain location. No location attribute is currently used, but it could be used in the future. | Info | All | 2014-02-12 |
| 1 | q and sort are GET parameters and have got nothing to do with the JSON payload. Therefore we don't see a current of future issue. | Info | All | 2014-02-12 |
| 1 | The REST API defines the following line as a return value. This is required and will not change.
You are correct in the assumption, that the following line will return the same information: Filtering, sorting and searching allows for the above query. |
Info | All | 2014-02-12 |
| 1 | Info | All | 2014-02-12 | |
| 1 | Info | All | 2014-02-12 |
