Skip to content

Support positioning custom processors relative to any existing processor#670

Merged
DarkaOnLine merged 4 commits into
DarkaOnLine:masterfrom
DerManoMann:processor-positioning
Jun 12, 2026
Merged

Support positioning custom processors relative to any existing processor#670
DarkaOnLine merged 4 commits into
DarkaOnLine:masterfrom
DerManoMann:processor-positioning

Conversation

@DerManoMann

Copy link
Copy Markdown
Contributor

Relates to #667

Summary

  • Custom processors in scanOptions.processors can now specify where they should be
    inserted in the pipeline using an array form: ['class' => ..., 'after' => ...]
  • Plain string/instance entries retain backwards-compatible behavior (inserted after BuildPaths)

Example

'processors' => [
    // Inserted after BuildPaths (default, backwards compatible)
    MyProcessor::class,

    // Inserted after a specific processor
    ['class' => AnotherProcessor::class, 'after' => AugmentSchemas::class],
],

@coveralls

coveralls commented Jun 11, 2026

Copy link
Copy Markdown

Coverage Status

coverage: 99.405% (+0.02%) from 99.39% — DerManoMann:processor-positioning into DarkaOnLine:master

@DarkaOnLine DarkaOnLine merged commit 8a27072 into DarkaOnLine:master Jun 12, 2026
6 checks passed
@DerManoMann DerManoMann deleted the processor-positioning branch June 12, 2026 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants