Releases: crwlrsoft/crwl-extension-utils
Releases · crwlrsoft/crwl-extension-utils
v2.3.1
Fixed
- It tries to cast step config values based on their configured type when using
StepBuilder::getValueFromConfigArray()
.
v2.3.0
Added
- New config param type multi line string (
ConfigParam::multiLineString()
/ ConfigParamTypes::MultiLineString
).
v2.2.0
Added
- New config param type float (
ConfigParam::float()
/ ConfigParamTypes::Float
).
v2.1.0
Added
- New classes
RequestTracker
and TrackingGuzzleClientFactory
. When steps need to execute HTTP requests without the HttpLoader
from the crawler package (for example when using some REST API SDK), developers are encouraged to utilize either a Guzzle Client instance generated by the TrackingGuzzleClientFactory
or invoke the trackHttpResponse()
or trackHeadlessBrowserResponse()
methods of the RequestTracker
manually after each request. This enables seamless tracking of requests within the crwl.io app.
v2.0.0
Changed
- Require
illuminate/support
, register ExtensionPackageManager
as a singleton via a new ServiceProvider
and remove ExtensionPackageManager::singleton()
and ExtensionPackageManager::new()
methods.
v1.1.0
Added
- New method
StepBuilder::setFileStoragePath()
. The app will call this method with the path where files can be stored, before the StepBuilder
builds any step. So inside the builder, when building a step, you can rely on this path.
v1.0.0
Nothing added. Just more tests, static analysis, code style fixing, CI pipeline on github and some documentation in the readme file, so it can be published (the package was still private until here).
v0.1.1
Added
ExtensionPackageManager::getPackages()
to get all registered packages.
Initial Release
This release contains:
- The abstract
StepBuilder
for that the crwl.io app can use to provide a step to the user.
- The
ExtensionPackageManager
where all packages and steps need to be registered.