Changes between Initial Version and Version 1 of Ticket #21890, comment 4


Ignore:
Timestamp:
03/05/2014 10:42:46 PM (16 months ago)
Author:
anubhav9042
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21890, comment 4

    initial v1  
    11From what I have understood, the changes occur first in {{{class Foo}}}, thus it now has a field {{{baz}}}. Then when applying changes in {{{class Bar}}}, when it sees that parent class is {{{Foo}}} and {{{Bar}}} has a field of same name as that in {{{Foo}}}, it raises {{{FieldError}}}.
    22
    3 What I think of solving this:
    43If such {{{FieldError}}} arises, then it should be caught and then we can create a whole new {{{Bar}}} or something like that.
     4Reordering will create subclass first, will it not be wrong creating a subclassbefore its base class
    55
    66
Back to Top