On Tue, Dec 9, 2014 at 9:29 AM, sri <[email protected]> wrote: > Well, it would require that changes to Changes adhere to some agreed upon >> convention of course... :) >> > > I try to give every Changes entry the same prefix > (Improved/Fixed/Deprecated...) and would love to see a wiki page with more > detailed upgrade instructions. > But i think it would have to be done manually and add more details/extra > examples, to actually be worth it. >
I have been following Mojolicious pretty religiously for over two years now. I'd be happy to commit to doing this, but I don't know that I understand changes well enough to devise examples. It generally takes me much longer to have that "aha" moment of the impact of such an improvement/fix/deprecation. Nevertheless, I would be more than willing to keep such a wiki updated to the best of my ability and perhaps at some point someone else would see the value who is more qualified to maintain it. As an example for a recent occurrence: Deprecated Mojo::DOM::siblings Alternative: Mojo::DOM::following_siblings and Mojo::DOM::preceding_siblings. (Is there a more appropriate word than "alternative"?) I would then link to commits, reference versions (effective 5.69, IIRC), and link to appropriate sections in documentation. Generally your changes also incorporate examples, so I reckon I wouldn't need an example for the new methods, but perhaps in showing something to the effect of what one used to do (e.g. render(partial=>1)) and what one should now do (e.g. render_to_string()) and then link to the doc for the latter. Does that sound about right and sufficient for what you were thinking would be necessary and desirable? -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
