Difference between revisions of "2013-12-05 Telephone Conference DEVROOM / stepping stone GmbH"
From stoney cloud
[unchecked revision] | [unchecked revision] |
(→Transcript) |
(→Transcript) |
||
Line 101: | Line 101: | ||
| width="40px" | 6 | | width="40px" | 6 | ||
| width="800px" | Search REST API: | | width="800px" | Search REST API: | ||
− | * | + | * Documentation will be updated to reflect the changes. |
− | | width="70px" | | + | | width="70px" | To Do |
− | | width="70px" | | + | | width="70px" | TMU/MEI |
| width="70px" | 2013-12-05 | | width="70px" | 2013-12-05 | ||
|- | |- |
Revision as of 15:02, 5 December 2013
Transcript of the Telephone Conference between DEVROOM / stepping stone GmbH
Location | Skype |
Date | Thursday, the 5th of December 2013 |
Time | 13:30 until 14:30 |
Participants |
|
Non participants |
|
Agenda |
|
Transcript
No. | Text | What? | Who? | When? |
---|---|---|---|---|
1 | Each resource collection:
|
To Do | TMU/MEI | 2013-12-05 |
2 | Do we return empty values (like shippingAddress) or not?
|
Info | All | 2013-12-05 |
3 | isActive is missing in the current examples.
|
To Do | TMU/MEI | 2013-12-05 |
4 | The logic of the deletion process is currently located on the client side. On the server we only return an error, it the item to be deleted still has dependencies.
|
Info | All | 2013-12-05 |
5 | New Functionality in the REST api:
|
To Do | TMU/MEI | 2013-12-05 |
6 | Search REST API:
|
To Do | TMU/MEI | 2013-12-05 |
7 | Info | All | 2013-12-05 | |
8 | Info | All | 2013-12-05 |