meilisearch/crates/permissive-json-pointer
Lukas Kalbertodt 057fcb3993
Some checks are pending
Indexing bench (push) / Run and upload benchmarks (push) Waiting to run
Benchmarks of indexing (push) / Run and upload benchmarks (push) Waiting to run
Benchmarks of search for geo (push) / Run and upload benchmarks (push) Waiting to run
Benchmarks of search for songs (push) / Run and upload benchmarks (push) Waiting to run
Benchmarks of search for Wikipedia articles (push) / Run and upload benchmarks (push) Waiting to run
Run the indexing fuzzer / Setup the action (push) Successful in 1h4m31s
Add indices field to _matchesPosition to specify where in an array a match comes from (#5005)
* Remove unreachable code

* Add `indices` field to `MatchBounds`

For matches inside arrays, this field holds the indices of the array
elements that matched. For example, searching for `cat` inside
`{ "a": ["dog", "cat", "fox"] }` would return `indices: [1]`. For nested
arrays, this contains multiple indices, starting with the one for the
top-most array. For matches in fields without arrays, `indices` is not
serialized (does not exist) to save space.
2024-11-20 01:00:43 +01:00
..
src Add indices field to _matchesPosition to specify where in an array a match comes from (#5005) 2024-11-20 01:00:43 +01:00
Cargo.toml Move crates under a sub folder to clean up the code 2024-10-21 08:18:43 +02:00
README.md Move crates under a sub folder to clean up the code 2024-10-21 08:18:43 +02:00

Permissive json pointer

This crate provide an interface a little bit similar to what you know as “json pointer”. But its actually doing something quite different.

The API

The crate provide only one function called [select_values]. It takes one object in parameter and a list of selectors. It then returns a new object containing only the fields you selected.

The selectors

The syntax for the selector is easier than with other API. There is only ONE special symbol, its the ..

If you write dog and provide the following object;

{
  "dog": "bob",
  "cat": "michel"
}

Youll get back;

{
  "dog": "bob",
}

Easy right?

Now the dot can either be used as a field name, or as a nested object.

For example, if you have the following json;

{
  "dog.name": "jean",
  "dog": {
    "name": "bob",
    "age": 6
  }
}

What a crappy json! But never underestimate your users, they WILL somehow base their entire workflow on this kind of json. Here with the dog.name selector both fields will be selected and the following json will be returned;

{
  "dog.name": "jean",
  "dog": {
    "name": "bob",
  }
}

And as you can guess, this crate is as permissive as possible. Itll match everything it can! Consider this even more crappy json;

{
  "pet.dog.name": "jean",
  "pet.dog": {
    "name": "bob"
  },
  "pet": {
    "dog.name": "michel"
  },
  "pet": {
    "dog": {
      "name": "milan"
    }
  }
}

If you write pet.dog.name everything will be selected.

Matching arrays

With this kind of selectors you cant match a specific element in an array. Your selector will be applied to all the element in the array.

Consider the following json;

{
  "pets": [
    {
      "animal": "dog",
      "race": "bernese mountain",
    },
    {
      "animal": "dog",
      "race": "golden retriever",
    },
    {
      "animal": "cat",
      "age": 8,
    }
  ]
}

With the filter pets.animal youll get;

{
  "pets": [
    {
      "animal": "dog",
    },
    {
      "animal": "dog",
    },
    {
      "animal": "cat",
    }
  ]
}

The empty element in an array gets removed. So if you were to look for pets.age you would only get;

{
  "pets": [
    {
      "age": 8,
    }
  ]
}

And I think thats all you need to know 🎉