软工国外原课件11AdvancedRails.pptxVIP

DRYing Out MVC(ESaaS §5.1)? 2013 Armando Fox David Patterson, all rights reservedDon’t Repeat Yourself – But How?Goal: enforce that movie names must be less than 40 charactersCall a “check” function from every place in app where a Movie might get created or edited? That’s not DRY!How do we DRY out cross-cutting concerns: Logically centralized, but may appear multiple places in implementation?Background History: GO TO COME FROMCACM, 1968 Letter to EditorAspect-Oriented ProgrammingAdvice is a specific piece of code that implements a cross-cutting concernPointcuts are the places you want to “inject” advice at runtimeAdvice+Pointcut = AspectGoal: DRY out your codeRails Example: ValidationsSpecify declaratively in model classValidation is advice in AOP sense Many places in app where a model could be modified/updatedIncluding indirectly via associations!Don’t want model validation code in all these placesSo where are the pointcuts?/2GtWshSb/2GtWshSbModel Lifecycle CallbacksAllows Pre and Post OperationsValidation automatically happens here? or when you call valid?? if fail, save will failmodel.errors is an ActiveRecord::Errors object with cool behaviors of its own? See Screencast 7.1.1Example: Controller Filters/ybP6Ece1/ybP6Ece1Filters declared in a controller also apply to its subclassesCorollary: filters in ApplicationController apply to all controllersA filter can change the flow of executionby calling redirect_to or render You should add something to the flash to explain to the user what happened, otherwise it will manifest as a “silent failure”Validations vs. FiltersValidationFilterAdvice (DRYness)Check invariants on modelCheck conditions for allowing controller action to runPointcutAR model lifecycle hooksBefore and/or after any public controller methodCan change execution flow?NoYesCan define advice in arbitrary function?Yes; shortcuts provided for common casesYes, must provide functionInfo about errors?Each model object has associated errors objectCapture