New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TDLight branch #470
Comments
To consider: should TDLight branch have the same version as aiogram? e.g. "2.11.3" and "2.11.3-tdl" |
@MasterGroosha I think it'll be better to combine versioning like this: 2.11.3-tdl.0 < 2.11.3-tdl.1 (patch specific for tdlight) < 2.11.4-tdl.0 (new aiogram version) |
@evgfilim1 can we move this discussion to "Discussions"? |
If you have more to discuss, then why not |
I dont think it should be different branch of aiogram. I'd like idea of creating an extension as separated package and different releases schedule. Something like |
https://github.com/tdlight-team/tdlight-telegram-bot-api/blob/gh-pages/tdlight-api-openapi.yaml you can easily generate tdlight bot api objects using the open api schema |
Does this also concern the new user mode? |
yes |
Is your feature request related to a problem? Please describe.
A specific branch for https://github.com/tdlight-team/tdlight-telegram-bot-api/ - fork of botapi
Its features - https://github.com/tdlight-team/tdlight-telegram-bot-api#tdlight-features
Describe the solution you'd like
A specific branch would be fine.
Describe alternatives you've considered
Not relevant
Additional context
None
The text was updated successfully, but these errors were encountered: