Define what it means for an added property to conflict with an existing dynamic property

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • V4.0_ERRATA01
    • Affects Version/s: V4.0_OS
    • Component/s: Protocol
    • None
    • Environment:

      [Applied]

    • Hide

      It should be allowed to add a new prop/nav prop as long as any existing dynamic properties with that name are the same type, or derived from the same type, as the type defined for the new property. (Note: I was tempted to use "type-compatible" but I think that definition is a little too loose).

      Show
      It should be allowed to add a new prop/nav prop as long as any existing dynamic properties with that name are the same type, or derived from the same type, as the type defined for the new property. (Note: I was tempted to use "type-compatible" but I think that definition is a little too loose).

      Section 5.2 of Protocol currently says that adding properties/nav props are "safe" schema changes (not requiring a version change) as long as the added property/nav prop "does not conflict with an existing dynamic property".

      However, we don't say what "conflict" means.

            Assignee:
            Michael Pizzo (Inactive)
            Reporter:
            Michael Pizzo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: