oqapi/webgui
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document how to modify update, and why in general it shouldn't be done.

Browse source
This commit is contained in:
Colin Kuskie 2011-12-05 16:32:52 -08:00
parent 5fbf0cb10f
commit 2eb7b11880
1 changed files with 7 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/migration.txt
View file

@ -247,6 +247,13 @@ of type SomeClass, populated with information from the database.
WebGUI::Asset::SomeClass->new($propertyHashRef) will return you an object of type SomeClass populated
with the properties you have passed in. Missing properties will have default set from the definition.
Asset & Moose
-------------
The update method for Asset's now comes from WebGUI::Definition::Role::Object. Since the Asset base
class does not have an update method, you cannot use Moose's "override" method modifier to add
behavior to it. You must use "around" instead. Note, in most cases, you should never need
to do this, because it is much more modular to use modifiers on individual asset properties.
Exceptions
----------
All Asset instanciators, new, newById, newByUrl, newPending, newByPropertyHashRef throw exceptions instead