This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Resolve: Use new Extractor location #3918
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Task linked: OP-3882 Change extractor usage in resolve |
iLLiCiTiT
added
host: Fusion
type: refactor
|
Sorry - not running Resolve here. Can't easily test. |
jakubjezek001
approved these changes
Sep 27, 2022
iLLiCiTiT
deleted the
feature/OP-3882_Change-extractor-usage-in-resolve
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Brief description
Using new import source of Extractor in Resolve.
Description
Resolveextractors are using new location of
Extractorplugin. PR is related to #3771 .Testing notes:
All Resolve extractors should work