PROOF OF CONCEPT; DO NOT MERGE: Implement else

[KnorpelSenf]

Explanation for #136 (comment)

[KnorpelSenf]

Leaving this here in case someone is wondering how to do if-else statements.

let iff = bot.filter((ctx) => ctx.update.update_id % 4 === 0);
{
    iff.do((ctx) => ctx.reply("Div 4 has rem 0"));
}
let elsee = bot.else();
{
    iff = elsee.filter((ctx) => ctx.update.update_id % 4 === 1);
    {
        iff.do((ctx) => ctx.reply("Div 4 has rem 1"));
    }
    elsee = elsee.else();
    {
        iff = elsee.filter((ctx) => ctx.update.update_id % 4 === 2);
        {
            iff.do((ctx) => ctx.reply("Div 4 has rem 2"));
        }
        elsee = elsee.else();
        {
            elsee.do((ctx) => ctx.reply("Div 4 has rem 3"));
        }
    }
}
bot.do((ctx) => ctx.reply("Evaluation complete"));

Same thing but without brackets:

let iff = bot.filter((ctx) => ctx.update.update_id % 4 === 0);
    iff.do((ctx) => ctx.reply("Div 4 has rem 0"));
let elsee = bot.else();
    iff = elsee.filter((ctx) => ctx.update.update_id % 4 === 1);
        iff.do((ctx) => ctx.reply("Div 4 has rem 1"));
    elsee = elsee.else();
        iff = elsee.filter((ctx) => ctx.update.update_id % 4 === 2);
            iff.do((ctx) => ctx.reply("Div 4 has rem 2"));
        elsee = elsee.else();
            elsee.do((ctx) => ctx.reply("Div 4 has rem 3"));

Note that this is a pointless example because the if statements are all mutually exclusive but it still illustrates the point.

[KnorpelSenf]

If we ever figure that we do indeed want to merge this, we would need to add a protection against doing

bot.filter()
bot.use()
bot.else()

because that will be super confusing, as the else call and the use call are actually going to be swapped. else will be executed before use in case filter does not trigger.

[KnorpelSenf]

This only works with filter and on. It does not work with command or hears or any other composer method that uses multi-level filtering.