Graphql integration (concept) #152
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thehighestmath
approved these changes
Nov 30, 2025
Collaborator
|
Ok |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
В моих текущих реалиях (выгрузить 12 репо ~1700 PR) существующая реализация на githubapi работает очень медленно (последнее выполнение длилось почти 1.5 часа), в основном из-за поэлементного получения
GraphQL позволяет 1) описывать запрос для получения только нужной информации 2) получать список объектов (ограничение в 100 объектов + страничная логика). Имеет свои лимиты, но они слабо расходуются (1 запрос graphql условно может быть равен 1000 запросов к githubapi)
В качестве концепта (с закосом на расширение и как необходимость сейчас) сделал концепт для PR - та же информация, что в старом модуле (1700 PR), получается за ~ 3 минуты
P.S. код под flake8 починю потом (или не починю)