Mateo Nunez

That sounds great @micheleriva! I think it would be a good idea to implement the `sort` parameter (and thus the method), within the `search` function, to sort (using _occurrencies_ just...

@micheleriva I have prepared a [branch](https://github.com/nearform/lyra/compare/main...mateonunez:lyra:feat/occurrences-sort) with working (and incomplete) code for it. The `sort` options accepted are: `none` (as usual) and `relevance` (by occurrences). The "relevance" could be accepted...

Initially, this implementation affects a lot of the performance of the search action. Current timing: ```js { elapsed: '114μs', hits: [ { id: 'PmLDkPyPWlRPG5qFcmS_7', quote: "It's alive! It's alive!", author:...

I've tried it with **1M of documents**. The result is amazing! @micheleriva **Without implementation:** ```js { elapsed: '421ms', hits: [ { id: 'ZpRIoxvyzosuI6yNW47cx', quote: 'I saw them alive. Alive man....

I could work on it, but there is just one question to understand: what should Lyra do in case the `limit` parameter is set? Should it compute all occurrences (sort...

> Going "pseudo-logic": > > > > ```diff > > private async _insert({ doc, id, language }: QueueDocParams): Promise { > > const index = this.index; > > this.docs.set(id, doc);...

When the `getMockDispatch` method resolves the path, the **mockDispatches** are filtered by the `consumed` prop and the result of `matchValue` method, checking the following variables: ```js path: "/foo?foo=bar&key=get"; resolvedPath: "/foo?key=get&foo=bar"...

I've converted this PR into a draft, need to run the E2E tests locally and check for behaviors in `rest-operation` tests.

> I've wanted to say the same thing. Any ideas? I can also consider removing the MDX system. But I would like to improve how articles are rendered.

Hey @Rivalakmalll, thank you for the appreciation! You can find the image picture right here: `public/images/profile.jpg`