Thomas Raffray

Hey! Coming from my duplicate [#263](https://github.com/json-editor/json-editor/issues/263) (sorry about that!) I had the same problem at work, and I had to come up with a quick fix to handle the large...

@j2jensen I looked at your code (but didn't test it), and asked myself a question. When I tried to improve the performance on my side, I stumbled upon some edge...

@j2jensen Okay, let me know when you have time to work on it. Apart from item edition, I had to check that headers stay updated, and I didn't take time...

Hey everyone! I'm upping this topic since it's still something I would like to help improving :) I'm working with it since january, and no issue seems to have been...

Actually, I work with very large JSON objects everyday, but my company won't let me give them to you as tests 😀 I will try to come up with some...

_There was, indeed, pushback_

Hey @georgantasp 👋🏻 I'm really sorry we took so long to get back to you. We can't merge your PR as-is because it would introduce breaking changes, which we won't...

I'll get back to you on Monday about this alternative, I didn't think about the fact it would be painful to unmarshal the same prop into two different types About...

@georgantasp you're right that it may not be the most efficient way to solve this issue, in the end. We better not double the amount of memory consumption (for holding...

Forgot to add an example, so it's more clear: [here is the search method](https://github.com/algolia/algoliasearch-client-go/blob/84d4bcddbc6477a8c32825f881e8faa43a64c386/algolia/search/api_search.go#L8525), returning the raw data from the API call, in the beta version of the client