From 2eb7b11880a314c6aefed8b52d0b2fb839353989 Mon Sep 17 00:00:00 2001 From: Colin Kuskie Date: Mon, 5 Dec 2011 16:32:52 -0800 Subject: [PATCH] Document how to modify update, and why in general it shouldn't be done. --- docs/migration.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/migration.txt b/docs/migration.txt index 5910b1266..b88aa7af1 100644 --- a/docs/migration.txt +++ b/docs/migration.txt @@ -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