Add --convert option from Hoogle4 #376
Open
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
Reason: in situation where one cannot use the shell postprocessing it is easier to output one entry per one line for which JSONL is suitable.
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.
Adds feature not ported from Hoogle4, as noted in #373.
This re-introduces the
--convertflag which takes a list of text databases to index into the binary format.This is a more strict version of
--local=directory, since this will only read the specific files listed on the command line, whereas the--localoption will read all.txtfiles, even those that might not parse.In my use case, I don't need the hoogle server as I just use the CLI lookup. So, it seems unclear what the behavior should be when serving a text database through the server interface. I suppose it is possible to point Hoogle to the right documentation directory where it could find the rest of the Haddock docs. If you have any suggestion for this murky support for the server interaction, I'm open to fixing it.