-
Notifications
You must be signed in to change notification settings - Fork 32
[Feature] Support NDJson and CSV #262
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
Conversation
brunoocasali
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left some comments, but in fact I think solving the conflicts will help a lot!
| /// * the passed [documents] must be a valid JSON string representing an array of objects. | ||
| /// * If index does not exist, it tries to create a new index and adds documents. | ||
| Future<Task> addDocumentsJson( | ||
| String documents, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The best way to represent the JSON docs is to receive it as string?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The current addDocuments already receives a parsed json, all these new methods mainly target file contents, so all of them must be raw strings.
or is that not the case ?
|
I have reworked document tests to be more structured and removed some repetitive code, I also organized the comments in macro templates. |
brunoocasali
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot @ahmednfwela 🎉
bors merge
|
Build succeeded: |
Fixes #102
Depends on #261