Remove deprecated output parser in favor of converters #1596
Conversation
This file contains hidden or 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
…ject All output parser functionality has already been migrated to the converter package since milestone M1. Changes: - Replace all instances of 'parser' with 'converter' in variable names and test cases - Delete (pre M1) deprecated parser package and all associated classes - Remove Output Parsers section from README.md - Update Javadoc comments to reference converters instead of parsers
|
LGTM, merging after resolving the conflict. |
|
Resolved the conflicts, rebased and merged as 33a7241 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
All output parser functionality has already been migrated to the converter package
since milestone M1.
Changes: