Add Export Format Choice GUI #88
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
… handle these gracefully and even with these fixes exports of incomplete corpuses will likely just break silently and never finish.
Codecov Report
@@ Coverage Diff @@
## main #88 +/- ##
==========================================
+ Coverage 69.06% 69.09% +0.02%
==========================================
Files 47 47
Lines 1862 1867 +5
==========================================
+ Hits 1286 1290 +4
- Misses 576 577 +1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Added components to select different output formats when clicking export. Currently planning LangChain and OpenContracts format for starters. Probably makes sense to export to Spacy's document format too. Only OpenContracts is enabled at the moment, though, be warned, if you run into parsing issues importing a doc the export for the corpus containing the unparsed doc will break. Need to make the exporter more robust.