Download the PHP package pascalheidmann/mago-jms-serializer without Composer
On this page you can find all versions of the php package pascalheidmann/mago-jms-serializer. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pascalheidmann/mago-jms-serializer
More information about pascalheidmann/mago-jms-serializer
Files in pascalheidmann/mago-jms-serializer
Package mago-jms-serializer
Short Description Mago analyzer plugin that treats JMS Serializer annotated/attributed properties as externally read and written, avoiding false unused-property / write-only-property findings.
License MIT OR Apache-2.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package mago-jms-serializer
mago-jms-serializer
A Mago analyzer plugin that marks JMS Serializer annotated/attributed properties as read and written externally.
JMS populates these properties via reflection at (de)serialization time —
never explicitly assigned or read in PHP source — so Mago's native analyzer
would otherwise report them as unused-property / write-only-property.
This plugin registers a BeforeAnalysisHook that feeds synthetic
read/write references into Mago's own reference graph for any property
carrying a JMS\Serializer\Annotation\* attribute, so those findings
disappear without a baseline entry.
Installation
Configuring the worker
Mago plugins run inside a separate PHP process ("extension host") that Mago
starts and talks to over a small protocol — this package ships only the
Plugin class, not that process. Your project needs a small worker script
and a mago.toml entry pointing at it.
1. Create a worker entry point, e.g. mago/worker.php:
2. Register it as an extension host in mago.toml:
3. Verify it's wired up:
Scoping the scan (optional)
By default JmsPropertyPlugin scans every class Mago knows about, including
everything under vendor/ you've told Mago to include for symbol
resolution. For a large codebase that's needless work, since JMS attributes
only ever live in your own code. Pass one or more namespace prefixes to
restrict the scan:
This is a pure performance knob — it does not change which properties get suppressed, only how many classes the plugin has to look at to find them. On a mid-sized monorepo this cut analysis time from ~13.5s to ~3.5s with identical findings.
Multiple plugins in one worker
If you have other Mago plugins, one worker process can host all of them:
License
Dual-licensed under Apache-2.0, at your option — matching Mago itself.
