Hi @syntx

I'm not really seeing how this structure would go down. It's also missing tests. Can you please add tests for expected and failing bahavior? They will be needed for the PR anyway and it might help me understand what this is supposed to do.

Pieter

Hi @Eldinnie,

I've added a new test in test_conversationhandler.py (test_nested_conversation_handler).
The test shows the nested mapping options made available by this simple yet powerful change. Please take a look at the definition of "drinking_map_to_parent" for 5 different options:

    self.drinking_map_to_parent = {
        # Option 1 - Map a fictional internal state to an external parent state
        self.REPLENISHING: self.BREWING,
        # Option 2 - Map a fictional internal state to the END state on the parent
        self.STOPPING: self.END,
        # Option 3 - Map the internal END state to an external parent state
        self.END: self.CODING,
        # Option 4 - Map an external state to the same external parent state
        self.CODING: self.CODING,
        # Option 5 - Map an external state to the internal entry point
        self.DRINKING: self.DRINKING
    }

Just wanna say, nice solution a problem that came up a couple times already. I never thought it was worth it implementing something cause there didn't seem to be a neat solution, but i think this is good. Even allows you to go up the conversation handler tree arbitrarily high, which is even better. If we have a bit more documentation and an example for this, I'd approve this PR. Oh and there's a couple flake8 errors in the tests.