Skip to content

Deprecate the PHAR metadata #1152

@theofidry

Description

@theofidry

Feature Request

Setting the PHAR metadata was supported because it was a PHAR option. I am however not convinced this is a good thing as:

  • I never saw a good practical example.
  • It used to expose to security risks and in a way still does. And by design there is no control about how the metadata is set.

One notable exception is @llaville's https://github.com/llaville/box-manifest. That being said the core of the project is to provide a manifest in different formats and I am not convinced using the metadata here is a good idea (and Box should offer another way than relying on the metadata setting to achieve this).

Thoughts @sebastianbergmann @theseer? Do you have a use case for the PHAR metadata?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions