WAPI.loadEarlierMessagesTillDate enters infinite loop if the earliest message is posterior to the requested time

Current implementation of loadEarlierMessagesTillDate is

window.WAPI.loadEarlierMessagesTillDate = function (id, lastMessage, done) {
    const found = WAPI.getChat(id);
    x = function () {
        if (found.msgs.models[0].t > lastMessage) {
            found.loadEarlierMsgs().then(x);
        } else {
            done();
        }
    };
    x();
};

This tries to retrieve earlier messages even if the chat doesn’t have any, which may cause an infinite loop. The fix would be something in the lines of:

window.WAPI.loadEarlierMessagesTillDate = function (id, lastMessage, done) {
    const found = WAPI.getChat(id);
    x = function () {
        if (found.msgs.models[0].t > lastMessage && !found.msgs.msgLoadState.noEarlierMsgs) {
            found.loadEarlierMsgs().then(x);
        } else {
            done();
        }
    };
    x();
};

[smashah]

@OskJonsdottir You should suggest this change in this repo: https://github.com/mukulhase/WebWhatsapp-Wrapper as the wapi.js is taken from here: https://github.com/mukulhase/WebWhatsapp-Wrapper/blob/master/webwhatsapi/js/wapi.js

[OskJonsdottir]

@danielcardeenas Apparently someone fixed this in the original WAPI repo now…

https://github.com/mukulhase/WebWhatsapp-Wrapper/commit/da1dd396e769e3d812a55f929013ab570503d3f3#diff-ab0d21a115b41c44e1ec163f3a78f078R492

Maybe we can update wapi.js in this repo to pull the fix?