On Wednesday, August 19, 2015 at 3:21:54 AM UTC-5, Edward K. Ream wrote: > > On Tue, Aug 18, 2015 at 8:35 PM, David McNab <[email protected]> > wrote: > >> How does @clean handle it when a teammate does a major restructure of a >> module? For example, refactors a Python class into a base, a derived plus a >> mixin, and moves 4 global functions into the base class as methods, and >> moves 3 methods of the class out into functions? >> > > @clean never inserts or deletes nodes. The changes will be shoehorned somehow into existing nodes. [snip] > Furthermore, git or any other sccs will check your work, so there should be no serious worries.
I should explain further. Suppose you reorganize your .leo file to better represent a major restructuring done by your teammates. As long as the order of functions in the outline matches the restructured source file, git should report no changes *at all*. If git *does* report a change, you can simply use git to revert the change and then reopen the outline. Your outline *structure* will be as it was when you last saved the (reorganized) outline. The git revert (checkout) will simply update the *contents* of the reorganized outline. Save the outline again, and then verify that git reports no more changes. This workflow guarantees that your colleagues will never be affected by Leo, unless you want to reorganize *their* work. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor. For more options, visit https://groups.google.com/d/optout.
