Why is unioning bridge.BridgeExtContext and bridge.BridgeApplicationContext not allowed? | Pycord | Page 1

thorn halo Feb 2, 2024, 11:20 AM

#

So I recently updated the library to the latest commit with the new type checking stuff and It flagged out a few things including the usage of ctx: Union[bridge.BridgeExtContext, bridge.BridgeApplicationContext]. I only do this because specifying ctx: BridgeContext causes type warnings in my IDE (Pycharm) when I use stuff like ctx.guild and ctx.bot. Is there a reason why? and is there an alternative type to specify, and if, its bridge.BridgeContext can you please fix it to contain all the commonly shared attributes between bridge.BridgeExtContext and bridge.BridgeApplicationContext?

river pollen Feb 2, 2024, 1:30 PM

#

I had the same issues with it

thorn halo Mar 2, 2024, 9:44 AM

#

Looking at the 2.5 release, #2106 seems to be the solution. I will test and see if it works

GitHub

feat(ext.bridge): add `bridge.Context` as a Union class by OmLanke ...

Summary

Adds a shortcut Union class for BridgeExtContext, and BridgeApplicationContext.
Since bridge.BridgeContext is an ABC, using that as a typehint doesn't display the attributes and method...

thorn halo Mar 2, 2024, 12:43 PM

#

and it doesn't work

#

it still triggers the TypeError

#Why is unioning bridge.BridgeExtContext and bridge.BridgeApplicationContext not allowed?