hirrolot
I got a similar error: ``` error: failed to select a version for the requirement `serde = "^0.0.1"` candidate versions found which didn't match: 1.0.138, 1.0.137, 1.0.136, ... location searched:...
Ok, I'll open an issue in `dptree` that discusses implementation strategies then.
Sounds good to me. However, before implementing it, I think we should refactor `teloxide-macros` first (the code is quite dirty).
We discussed this issue in our development chat some time ago and didn't come to any implementation ideas. Also, it seems that other bot frameworks don't provide facilities for bot...
> However this also has an advantage: we don't need to make changes to teloxide when we are adding something to teloxide-core (this is both an advantage and a disadvantage)....
I can take this issue if you don't mind.
@WaffleLapkin, it seems that the next `teloxide-core` release is breaking. I think we can make a PR for this issue by the release then, WDYT?
Nice! But in the disadvantages of global re-export, you've mentioned: > We can't expand something from -core in a nice way What do you mean by it?
Since I don't see any issues with global re-export then, I'm closing this as resolved.
Indeed a vital feature for error handling. I would like to implement it via https://github.com/teloxide/teloxide/issues/694, since it would allow us to access the whole DI context inside the handler, not...