Raise an exception if dialog with MessageInput is started with StartMode.NEW_STACK parameter

[t3m8ch]

If you start the dialog with MessageInput with StartMode.NEW_STACK, the messages are ignored by the bot, as if the dialog is not started.

from aiogram_dialog import Dialog, Window, DialogManager, DialogRegistry, StartMode
from aiogram_dialog.widgets.input import MessageInput
from aiogram_dialog.widgets.text import Const
from aiogram import Bot, Dispatcher
from aiogram.types import Message
from aiogram.dispatcher.filters.state import State, StatesGroup
from aiogram.contrib.fsm_storage.memory import MemoryStorage

import asyncio
import logging
import os

TOKEN = os.getenv("TOKEN")


class DialogSG(StatesGroup):
    input_name = State()
    input_age = State()


async def on_input_name(msg: Message, dialog: Dialog, manager: DialogManager):
    manager.current_context().dialog_data["name"] = msg.text
    await dialog.next()


async def on_input_age(msg: Message, dialog: Dialog, manager: DialogManager):
    if not msg.text.isnumeric() or int(msg.text) < 0:
        await msg.answer("Not correct")
        return

    await msg.answer(
        f"Name: {manager.current_context().dialog_data['name']}]\n"
        f"Age: {msg.text}"
    )
    await manager.done()


dialog = Dialog(
    Window(
        Const("Input name"),
        MessageInput(on_input_name),
        state=DialogSG.input_name,
    ),
    Window(
        Const("Input age"),
        MessageInput(on_input_age),
        state=DialogSG.input_age
    ),
)


async def handler(msg: Message, dialog_manager: DialogManager):
    await dialog_manager.start(DialogSG.input_name, mode=StartMode.NEW_STACK)


async def main():
    logging.basicConfig(level=logging.INFO)
    storage = MemoryStorage()
    bot = Bot(token=TOKEN)
    dp = Dispatcher(bot, storage=storage)
    registry = DialogRegistry(dp)
    registry.register(dialog)
    dp.register_message_handler(handler, commands=["start"])

    await dp.start_polling()


if __name__ == "__main__":
    asyncio.run(main())

This behavior is due to the fact that MessageInput is used only in the stack by default. Using this widget with other stacks is unacceptable behavior, so an exception should be thrown so that the developer does not wonder why the bot ignores messages.

[Tishka17]

Not sure about exception, but could be a warning.
Also window switches might be also processed

[t3m8ch]

Not sure about exception, but could be a warning. Also window switches might be also processed

The developer may not have logging enabled. Also, I'm not sure that this bot's behavior is not an error, which should throw an exception.

[Tishka17]

in #164 inputs are supported via reply to message in non-default stack. Anyway we need at least on button there