Skip to content

Document which changes to properties are unsafe vs safe to do (Changing ancestor class declaring property, changing visibility of property) #137

@TysonAndre

Description

@TysonAndre

And compare this with serialize()/unserialize()

If it varies between php versions, document that.

Add unit tests that properties get unserialized properly for the safe cases.

  • They're all unsafe (no fallback to protected/private/public with same name at the moment)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions