Method PUT: ignore specification of protected properties which can not be set. Filtering them out of the payload list. This lets the result of a get using: class/id?@protected=true&@verbose=0 be used as input to a PUT operation without having to strip the protected properties. Note this does not raise an error if the PUT protected property is different from the value in the db. If the property is different but the etag/if-match passes, the user attempted to set the protected property and this should result in an error, but will not with this patch. Method DELETE class/id/attribute: raise error when trying to delete protected or required attribute/property. Raise UsageError when attribute doesn't exist. Method PATCH class/id: raise error when trying to replace/remove protected attribute/property raise error when trying to remove required attribute/property Catch KeyError at top level and turn into 400 error. If payload has an attribute/property that does not exist, raise UsageError which becomes a 400 error.

=======================================================
Roundup: an Issue-Tracking System for Knowledge Workers
=======================================================

For how to contact the community see http://www.roundup-tracker.org .

Contents
========

.. toctree::
   :maxdepth: 2

   features
   installation
   upgrading
   FAQ
   user_guide
   customizing
   admin_guide
   debugging
   xmlrpc
   rest
   overview
   Design (original) <design>
   developers
   tracker_templates
   Notes about the MySQL Database backend <mysql>
   Notes about the PostgreSQL Database backend <postgresql>
   glossary
   acknowledgements
   Richard Jones implementation notes <implementation>
   license