Details

    • Type: Improvement
    • Status: Closed
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: 1.0.1
    • Fix Version/s: 1.0.2
    • Labels:
      None
    • Similar issues:
    • Epic Link:
    • Sprint:
      Platform166: GA (truly,really)
    • Processed by team:
      Platform

      Description

      Serialization of resource values (values stored in a separate resource file) currently is using several pre and post processing steps and logic spread across ModuleWriter, ModuleContext and SourceSerializer implementation(s).
      This complicates further/future maintainability and extendability while the logic and requirements (now) have been fleshed out enough to allow refactoring this in a more straightforward way.

      To simplify the resource values serialization the following changes are needed:

      • serialize resources during serialization of a source instead of afterwards via a PostProcessItem (CopyItem or BinaryItem)
      • move the responsibility for serialization to the ModuleContext (to be invoked from the SourceSerializer)
      • ModuleWriter and SourceSerializer will explicitly (and thus only) use model implementation classes like ModuleImpl, DefinitionNodeImpl, DefinitionPropertyImpl, ValueImpl, etc. to no longer need to use awkward casts where it matters

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                adouma Ate Douma
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: