Weave Code
Parser Common Laravel Package
abuseio/parser-common
Common library providing shared parser components for AbuseIO: base parser classes, helper utilities, and conventions for building and running abuse-report parsers. It reduces duplication across AbuseIO parser packages and standardizes parsing workflows.
This is the helper package that is required for all parsers
Frequently asked questions about Parser Common
- What is abuseio/parser-common used for?
- It is the shared helper package for AbuseIO parsers. It provides base parser classes, helper utilities, and conventions so parser packages do not duplicate common parsing workflows. Most AbuseIO parser packages require it as a dependency.
- Do I need to install abuseio/parser-common separately?
- Usually no. It is a required dependency of AbuseIO parser packages, so Composer installs it automatically when you require a parser. Install it directly only if you are building your own parser or need the shared base classes.
- How do I install abuseio/parser-common with Composer?
- Run composer require abuseio/parser-common in your Laravel or AbuseIO project. Composer resolves the appropriate version from Packagist and installs its dependencies. If you are developing a parser package, add it to your package's require section instead.
- Which Laravel versions support abuseio/parser-common?
- Check the package's composer.json and Packagist release metadata for the exact Laravel and PHP constraints. Because it is a shared AbuseIO library, its compatibility is tied to the AbuseIO version and parser ecosystem you use. Pin compatible versions in composer.json and test upgrades in a staging environment.
- How do I create a custom AbuseIO parser using the base classes?
- Extend the provided base parser classes and follow the conventions documented by AbuseIO. Implement the required parsing methods and register your parser within the AbuseIO installation. Keep parser-specific logic in your package and reuse the common helpers for shared behavior.
- Can I use abuseio/parser-common outside of AbuseIO?
- It is designed for AbuseIO parser development, so using it outside that ecosystem may add unnecessary dependencies. The base classes and utilities assume AbuseIO parser conventions. For general Laravel parsing tasks, a standalone package is usually a better fit.
- How do I configure parser-common for my parser package?
- Configuration is typically handled by the consuming parser package rather than parser-common itself. Follow your parser's README and AbuseIO configuration conventions for registration and runtime settings. Review the source for available helper methods before adding custom configuration.
- Is abuseio/parser-common suitable for production?
- Yes, it is intended to support production AbuseIO parser workflows as a shared dependency. Treat it like any Composer dependency: pin versions, review changelogs, and test parser behavior before deploying. Production suitability also depends on the specific parser package and your AbuseIO setup.
- How do I test a parser built on abuseio/parser-common?
- Write tests against your concrete parser class while relying on parser-common for base behavior. Use your normal Laravel testing setup or PHPUnit, and mock external abuse-report inputs. Verify parsing output and error handling rather than testing the shared library internals.
- What are alternatives to abuseio/parser-common?
- Alternatives depend on your goal: use the official AbuseIO parser packages for supported feeds, or build custom parsing code if you are not using AbuseIO. There is no drop-in general-purpose replacement for this AbuseIO-specific helper library. Evaluate maintenance and compatibility before choosing a different approach.
Weaver
How can I help you explore Laravel packages today?