Skip to content

Ideas #1

@thunderer

Description

@thunderer

Just a couple of ideas to remember:

  • introduce other formats - TOML, MsgPack, ProtoBuf,
  • DateTimeNormalizer using passed format,
  • do not check whether class or interface exists when registering a handler,
  • think about multiple handlers based on the object state - "normalizer resolvers",
  • hybrid normalizer + hydrator registration for single class, that can maybe share the context?
  • XmlFormat::parse() does not include element attributes,
  • XmlFormat is unable to serialize element attributes,
  • add Context to both directions,
  • add normalization and hydration context with custom information (root object, parent object, maybe Request instance and so on),
  • add setDefault() to normalizer and hydrator containers,
  • allow more than one instance of object in cycle detection like Symfony Serializer does,
  • PublicPropertiesNormalizer (done with GetObjectVarsNormalizer),
  • find a way to set max nesting limit - nesting resolver called instead of current one,
  • split HandlerContainer into separate classes for normalizers and hydrators and remove alias from method adding normalizers (required in XML format),
  • release first version,
  • add DoctrineProxyNormalizer or fallback for class parents,
  • SerializardFacade.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions