You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We need the actual full result mode – output the entire subdocument that matches the query.
Describe the solution you'd like
Consider the query $.a..b[*], and the JSON:
This includes a revamp of all the internals that would be too long to describe in the log.
In short:
- `memmem` was rewritten to a custom implementation (courtesy of @charles-paperman)
- Each of the result modes has a separate `Recorder` that takes care of producing the results
- The results are written to a `Sink`, provided by the user; this might be a `Vec`, the stdout,
or some other `io::Write` implementation.
- Matches contain the full byte span of the value matched.
- A lot of `Input` and classifier APIs have massive breaking changes to accomodate this.
Ref: #56
Co-authored-by: cha <charles.paperman@univ-lille.fr>
Is your feature request related to a problem? Please describe.
We need the actual full result mode – output the entire subdocument that matches the query.
Describe the solution you'd like
Consider the query
$.a..b[*]
, and the JSON:Then in the output we should find all the following paths, separated with newlines:
Describe alternatives you've considered
Non-nested subdocument result mode tracked by #57
Additional context
This should be compatible with #54. Example output for the above JSON:
The text was updated successfully, but these errors were encountered: