{23} Trac comments (3729 matches)

Results (2301 - 2400 of 3729)

← 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 →
Ticket Posixtime Author Newvalue
#628 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#629 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#630 1285348178000000 johnbywater Referencing ticket #572 has changed sprint.
#632 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#633 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#633 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#634 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#634 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#635 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#635 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#636 1284689350000000 johnbywater Referencing ticket #579 has changed sprint.
#641 1284689330000000 johnbywater Referencing ticket #577 has changed sprint.
#644 1284689350000000 johnbywater Referencing ticket #579 has changed sprint.
#645 1284750525000000 johnbywater Moved from sprint 1.2.3
#645 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#645 1285957164000000 johnbywater Referencing ticket #572 has changed sprint.
#645 1286786420000000 johnbywater Referencing ticket #572 has changed sprint.
#645 1287392122000000 johnbywater Referencing ticket #572 has changed sprint.
#650 1286789277000000 johnbywater Moved from sprint 1.2.7
#655 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#656 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#657 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#658 1285252726000000 johnbywater Referencing ticket #655 has changed sprint.
#662 1286993727000000 johnbywater It might be natural for the locator of the rating for a package to be "/package/{id}/rating". I've got not idea what I meant by "An issue for CKAN too." I may have intended to log this againt ckanclient. Anyway, it seems to be just a CKAN thing. :-) I think I would like to do this: $data = c.package_register_post({'name': 'example'}) $data['title'] = 'Example' c.package_entity_put($data['id'], $data) and this: $data = c.package_entity_get('example') $data['title'] = 'Example' c.package_entity_put($data['id'], $data) I don't think either work. We could write a test for each. I think this does work: $data = c.package_entity_get('example') $data = c.package_entity_put($data['id'], $data) $data['title'] = 'Old Example' c.package_entity_put($data['id'], $data) Which is inconsistent. The reason is that the data returned by the update operation ("entity put") isn't given the same treatment as the read and create operations, which adds various read-only values. That's as far as I got. I inferred that one or several of the read-only values, when present in the update request data, cause the update to fail. I'm not sure how it fails. Rather than cutting down the response data, we could make the update call more robust. One fix would pick out from the request package data only the attributes that are permitted. A alternative fix would make what ever is choking on the extra values ignore them. I mean, ids are read-only, but we wouldn't want to reject an update because it has an id in the data. We do need to be careful about loading up the package entity data, but the 'id' is read-only and we aren't going to quible about that being present in the data of an update request (even if it doesn't match the referenced entity). I would rather not support "replace the entire package" with especial functionality and documentation. I think the model create/update/delete, where update is "set attributes" is sufficient, simple, and fairly optimal. To obliterate all registerd values without deleting, I would get the package entity data, loop over the keys and set the values to '', [] or {} depending on the type, and then PUT the entity. We could write a test for that.
#669 1286789428000000 johnbywater Moved from sprint 1.2.7
#669 1287392123000000 johnbywater Moved from sprint 1.2.8
#669 1287776309000000 johnbywater Moved from sprint 1.2.9
#669 1288038146000000 johnbywater Moved from sprint 1.3.0
#670 1286789428000000 johnbywater Moved from sprint 1.2.7
#670 1287392123000000 johnbywater Moved from sprint 1.2.8
#670 1287776309000000 johnbywater Moved from sprint 1.2.9
#670 1288038146000000 johnbywater Moved from sprint 1.3.0
#671 1286789428000000 johnbywater Moved from sprint 1.2.7
#671 1287392123000000 johnbywater Moved from sprint 1.2.8
#671 1287776309000000 johnbywater Moved from sprint 1.2.9
#671 1288038146000000 johnbywater Moved from sprint 1.3.0
#672 1286789428000000 johnbywater Moved from sprint 1.2.7
#672 1287392123000000 johnbywater Moved from sprint 1.2.8
#672 1287776309000000 johnbywater Moved from sprint 1.2.9
#672 1288038146000000 johnbywater Moved from sprint 1.3.0
#673 1286786420000000 johnbywater Referencing ticket #568 has changed sprint.
#674 1286786419000000 johnbywater Referencing ticket #568 has changed sprint.
#675 1286786420000000 johnbywater Referencing ticket #568 has changed sprint.
#675 1287392122000000 johnbywater Referencing ticket #568 has changed sprint.
#675 1287776309000000 johnbywater Referencing ticket #568 has changed sprint.
#677 1286786420000000 johnbywater Moved from sprint 1.2.6
#677 1287392123000000 johnbywater Moved from sprint 1.2.8
#677 1287746221000000 johnbywater Just to say, in cases where something needs to be delivered by somebody else, it can be useful to create a separate task ticket (with undefined remaining time) to indicate what deliverable is being waited on, and in the sprint backlog to drag it above the ticket(s) that depend on the deliverable. That means we don't feel a need to factor unknowable waiting time into our own tasks. It also means impediments are more obviously displayed, so you don't lose track when waiting for a number of things. The two different objectives also well separated so there is no question that somebody is stuck and passing time on a task. I've done this a few times recently and it does help to keep things simple. :-)
#677 1287776309000000 johnbywater Moved from sprint 1.2.9
#677 1288038147000000 johnbywater Moved from sprint 1.3.0
#678 1286786420000000 johnbywater Moved from sprint 1.2.6
#679 1286786420000000 johnbywater Moved from sprint 1.2.6
#679 1287392123000000 johnbywater Moved from sprint 1.2.8
#679 1287776309000000 johnbywater Moved from sprint 1.2.9
#679 1288038147000000 johnbywater Moved from sprint 1.3.0
#681 1286786420000000 johnbywater Moved from sprint 1.2.6
#681 1287392123000000 johnbywater Moved from sprint 1.2.8
#681 1287776309000000 johnbywater Moved from sprint 1.2.9
#682 1286786420000000 johnbywater Moved from sprint 1.2.6
#682 1287392123000000 johnbywater Moved from sprint 1.2.8
#682 1287776309000000 johnbywater Moved from sprint 1.2.9
#682 1288038147000000 johnbywater Moved from sprint 1.3.0
#689 1287392122000000 johnbywater Referencing ticket #572 has changed sprint.
#689 1287776309000000 johnbywater Referencing ticket #572 has changed sprint.
#690 1288013610000000 johnbywater This concern was resolved in favour of a converged set of attributes (#711).
#696 1287392123000000 johnbywater Moved from sprint 1.2.8
#703 1288355926000000 johnbywater Referencing ticket #700 has changed sprint.
#703 1288356182000000 johnbywater Referencing ticket #700 has changed sprint.
#704 1288355926000000 johnbywater Referencing ticket #700 has changed sprint.
#704 1288356182000000 johnbywater Referencing ticket #700 has changed sprint.
#705 1288356302000000 johnbywater Referencing ticket #701 has changed sprint.
#705 1288356319000000 johnbywater Referencing ticket #701 has changed sprint.
#706 1288355926000000 johnbywater Referencing ticket #700 has changed sprint.
#706 1288356181000000 johnbywater Referencing ticket #700 has changed sprint.
#707 1288355926000000 johnbywater Referencing ticket #700 has changed sprint.
#707 1288356181000000 johnbywater Referencing ticket #700 has changed sprint.
#708 1288356302000000 johnbywater Referencing ticket #701 has changed sprint.
#708 1288356319000000 johnbywater Referencing ticket #701 has changed sprint.
#711 1288014219000000 johnbywater See also #504.
#712 1288038147000000 johnbywater Moved from sprint 1.3.0
#713 1288026226000000 johnbywater Referencing ticket #712 has changed sprint.
#713 1288038147000000 johnbywater Referencing ticket #712 has changed sprint.
#715 1289815657000000 johnbywater Moved from sprint 1.3.3
#718 1288195538000000 johnbywater Referencing ticket #716 has changed sprint.
#718 1288196547000000 johnbywater Referencing ticket #716 has changed sprint.
#718 1288197569000000 johnbywater Referencing ticket #716 has changed sprint.
#719 1288195538000000 johnbywater Referencing ticket #716 has changed sprint.
#719 1288196547000000 johnbywater Referencing ticket #716 has changed sprint.
#719 1288197569000000 johnbywater Referencing ticket #716 has changed sprint.
#720 1288195538000000 johnbywater Referencing ticket #716 has changed sprint.
#720 1288196547000000 johnbywater Referencing ticket #716 has changed sprint.
#720 1288197569000000 johnbywater Referencing ticket #716 has changed sprint.
#721 1288195538000000 johnbywater Referencing ticket #716 has changed sprint.
#721 1288196547000000 johnbywater Referencing ticket #716 has changed sprint.
#721 1288197569000000 johnbywater Referencing ticket #716 has changed sprint.
#722 1288195538000000 johnbywater Referencing ticket #716 has changed sprint.
#722 1288196547000000 johnbywater Referencing ticket #716 has changed sprint.
#722 1288197569000000 johnbywater Referencing ticket #716 has changed sprint.
#723 1288195538000000 johnbywater Referencing ticket #716 has changed sprint.
#723 1288196547000000 johnbywater Referencing ticket #716 has changed sprint.
← 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 →
Note: See TracReports for help on using and creating reports.