Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate if we should merge input-builder and input-extended #161

Open
simar0at opened this issue Jul 23, 2024 · 0 comments
Open

Evaluate if we should merge input-builder and input-extended #161

simar0at opened this issue Jul 23, 2024 · 0 comments
Assignees

Comments

@simar0at
Copy link
Member

We had a much different and more advanced implementation of input-extended in the dictQuery branch.
When merging I could not determine if the more advanced version can serve the same purpose as input-extended for the corpus query function.
Please evaluate if it makes sense to merge input-builder and input-extended and use it in dictQuery and corpusQuery or if we should keep this separate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants