Re: Catalyst begin/end methods

http://dev.catalystframework.org/old-wiki/wiki/FlowChart/—try that. It’s old but I believe it’s still accurate. I think your understanding of begin is closer to what auto is. You get one begin and one end unless you specifically code around it. The resolution would also be easy to test in any specific cases, I think, by looking at the debug output of the test server. FWIW, I can’t remember ever needing begin. It is probably an indication of design mistake that could be better handled with an attribute attached to the class.

Comment on Re: Catalyst begin/end methods Select or Download Code

Replies are listed 'Best First'.
Re^2: Catalyst begin/end methods by Anonymous Monk on Feb 12, 2015 at 01:04 UTC
https://metacpan.org/pod/distribution/Catalyst-Manual/lib/Catalyst/Manual/Intro.pod#Built-in-actions-in-controllers-autochaining seems to agree with that chart	[reply]
Re^3: Catalyst begin/end methods by Munkey (Novice) on Feb 12, 2015 at 08:21 UTC
thank you! I have ended up moving everything to auto, begin ( I was checking user permission to enter controller ) is better there anyhow - just return 0 to break flow, end ( preparing things for templates specific to that controller ) did not have to be in end, it was just a matter of taste I guess, and no logical reason to do it there. After reading the chart: my expectation was off, only the most specific match for begin and end is run. Auto does what I need here. Thank you for the information, I did not find the part on begin/end ( or overlooked it ) in the docs for some reason.	[reply]