Merge custom inspectors configuration with default one
Metadata
Current evaluation
Closed without a public fix. The enhancement to merge custom inspector configurations with defaults was deferred to internal tracking via Jira ticket FETCH-50. No code changes were merged.
Suggested action: —
No scores available.
Issue body
### What needs to get done
Load the custom inspector configuration given to the fetch-service as an override applied on top of the default configuration shipped with the fetch-service..
Apply the same strategy as the session inspectors configuration combination.
### Why it needs to get done
If a custom inspectors configuration is given to the fetch service, it is loaded **instead** of the default configuration shipped with the fetch-service. This behavior forces users (ex. the LP team) to regularly update their custom configuration whenever a new inspector is added, or when the default values change.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Closed without a public fix. The enhancement to merge custom inspector configurations with defaults was deferred to internal tracking via Jira ticket FETCH-50. No code changes were merged. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #210 Merge the inspector configuration branch | fetch-service | closed | The inspector configuration branch merge was closed without being merged or resolved. No pull request or conflict resolution occurred, leaving the task abandoned after an internal Jira ticket was created. |