Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • F FEDOT
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ITMO-NSS-team
  • FEDOT
  • Issues
  • #699

Closed
Open
Created Jun 02, 2022 by Elizaveta Lutsenko@LizLutsenkoOwner

Create a JSON Serializer for OptHistory

Created by: MorrisNein

A custom Serializer is needed that implies knowledge of OptHistory's inner structure. It must not contain or dump paths to classes used in OptHistory, thus it is to be immune to project structure changes. It must transform older histories to an actual form.

Potentially, it can resolve two major problems:

  1. Backward compatibility with older histories. by transforming every loaded history to an actual form.
  2. Compact storage of OptHistory. At least, it allows getting rid of mentioning paths to classes that take major space in default JSON dumps. At most, we can implement compact graphs storage (optional).
Assignee
Assign to
Time tracking