Publish a read-write field as read-only in the web service

Bug #316401 reported by Leonard Richardson
2
Affects Status Importance Assigned to Milestone
lazr.restful
Triaged
Wishlist
Unassigned

Bug Description

We have a way to publish a read-only attribute as read-write (by defining a mutator method that's invoked when the client tries to modify the attribute). We don't have the opposite: a way to prohibit writes through the webservice on a read-write field.

The original use case for this was IBug.private. The IBug.private problem was fixed another way, but it would have been easier to fix if we had @expose_as_readonly. The next time we have this kind of use case, let's fix it this way.

Tags: api
affects: launchpad-foundations → lazr.restful
Changed in lazr.restful:
importance: Undecided → Wishlist
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.