Hi @Bibo-Joshi, I would be happy to update the documentation with the discussed changes. However, I am a little unsure of what you mean by removing all mentions of (ext)._utils.

For example, in BasePersistence , do we remove all mentions of the custom typing aliases, leaving just a description?

A proposed example:

abstract get_user_data()
    Will be called by telegram.ext.Dispatcher upon creation with a persistence object. It should return the user_data if stored.
    
    Returns
        The restored user data.
    Return type
        DefaultDict[int]

Hi @Bibo-Joshi, I would be happy to update the documentation with the discussed changes

Sweet :) 👍

However, I am a little unsure of what you mean by removing all mentions of (ext)._utils.

Right, the persistence case is indeed a bit tricky. The point here is that in the usual case get_user_data should return a Dict[int, Dict], becaues context.user_data is usually of type Dict. However, if ContextTypes are used, then the it should return a Dict[int, context_types.user_data]. Maybe this can be formulated along the lines

abstract get_user_data()
    Will be called by telegram.ext.Dispatcher upon creation with a persistence object. It should return the user_data if stored, or an empty defaultdict. In the latter case, the defaultdict should produce values that correspond to the expected type of CallbackContext.user_data, which usually is simply dict unless ContextTypes are used.
    
    Returns
        The restored user data.
    Return type
        DefaultDict[int, Dict/Type specified by ContextTypes.user_data]

This is just a quick draft - feel free to reformulate :) A similar logic can be used for the other TypeVars in (.ext)._utils, i.e. describing which type is expected.
For type aliases (CDCData and ConversationDict), it should suffice to insert the actual type into the docs, replace ext._utils.ConversationDict with Dict[Tuple[:obj:`int`, ...], Optional[:obj:`object`]]

I hope this helps you get started :) If you have any questions, feel free to ping me here or on Telegram (@BiboJoshi)

All mentions of tg.(ext)._utils modules should have been removed, but please let me know if I missed any.

The changes also follow the discussed scheme, and I hope I haven't altered any key phrasing or meanings. Let know me if anything could be worded better and I would be happy to edit it :)

The past 4 commits have very similar messages as I didn't really know what to name them after the first one. Maybe we can squash them into 1 commit after all further documentation changes have been made?

Thank you for the contribution @kennethcheo :)