@piraces hi. Thanks a lot for providing this PR. I love that you added unit tests.
One issue I see with this approach is that the clients of the history have to change how they use it. And the debug console is not the only client (we also use it in most of the Input Boxes like Search and Extensions).
So idealy we would fix this without changing the API of the history. Can we just change the funtionality of the next and previous to handle this case and that we do not have to add hasPrevious and hasNext?

Hi @isidorn . For sure. I will make the changes only in the next and previous methods.
It is a good idea to mantain the hasPrevious and hasNext methods private and then use them in the public methods or I should do all the functionallity in the next and previous methods?

Thanks.

@piraces I would try to do everything in the next and previous if possible. However I leave that up to you since it is personal preference.

@isidorn I have finally made the commented changes. If there is another problem, please let me know.
Thanks.

Great PR, thanks for contributing. I have verified it nicely fixes the issue. Thus merging in.
🍻