| CARVIEW |
Navigation Menu
GitHub Community
[feature_request] GraphQL fetch user language information #18230
Replies: 89 comments · 7 replies
-
|
I fully concur with the assessment and feature request: For many purposes the languages a user uses is of interest, not languages used in a repository. This data is currently not accessible via the GraphQL API! |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 2 -
❤️ 4
-
|
I agree that this should be a feature. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 2 -
❤️ 2
-
|
Another nice feature would be an easy way to get the most recent commit date when inside Tree entries: https://www.reddit.com/r/graphql/comments/1338vwr/new_to_graphql_and_trying_to_understand_github/ |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 2
-
|
I buy this idea because I do a lot of work as a contributor to organizations repository, that shoul reflect on my profile as well |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1 -
❤️ 3
-
|
@Eminentzeal, please look at issue anuraghazra/github-readme-stats#1! |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 2 -
👀 2
-
|
👍 Agreed |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
-
|
I am voicing my support in an additional way. |
Beta Was this translation helpful? Give feedback.
All reactions
-
😄 1
-
|
I agree. I'm just learning to code and fork several projects to do so. After four projects and four months, the languages I used aren't in my top language stats. Any updates? |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 2 -
❤️ 1
-
|
This would be super useful |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
-
|
This should, indeed, be a feature. |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
-
|
Forks are as important for GH as own repos, so definitely should be a thing. |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
This comment was marked as spam.
This comment was marked as spam.
-
|
@Eagle3386 sorry, but you show blatant ridiculousness here, spamming the whole comment section with way more useless repeated comment. People should be able to comment whatever they want under a feedback discussion. While "+1" type of comments are not too useful, you commented mostly on a bunch that added some point(s). I have no idea what encouraged you to stop us in a hypocritical and comedic way. Also, do you realize:
|
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 1
-
|
I cannot agree more; it indeed will reflect more precisely and could allow counting for forks and other behaviours, especially when the repository is company-based and users are just collaborators. |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1 -
🚀 1
-
|
Thumbs up to this. My current stats look like I can only write Python but that is far from the truth as I use a large variety of languages but in company owned orgs. |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
This comment was marked as spam.
This comment was marked as spam.
-
|
Which I have done as well. Adding a further comment to show the different reasons this would be useful when this feature is developed could be useful to the devs. Certainly does not hurt. |
Beta Was this translation helpful? Give feedback.
All reactions
This comment was marked as spam.
This comment was marked as spam.
-
|
"new comments cause mails" - like the 10 emails I just got from you? 😄 It would be one thing if there were multiple new comments on this per day, but it's been fairly steady at one a week. If the mods disagree, they can delete comments and pin one asking only to up-vote and not comment. Not trying to be aggressive as I can see you were just trying to help. Just trying to show you the slight hypocrisy in your comment. The mods of this repo can manage the notifications if its a big issue for them. Same goes for anyone subbed to this issue. |
Beta Was this translation helpful? Give feedback.
All reactions
-
👍 6
-
|
+1, this would be a super handy addition. |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
-
|
support this! 👍 |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
-
|
Really need this 👍 |
Beta Was this translation helpful? Give feedback.
All reactions
-
❤️ 1
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1! This would be great |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
I agree it. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
+1 |
Beta Was this translation helpful? Give feedback.
All reactions
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There is currently no way to fetch the languages a specific user uses. The current
repositories/languagesobject of the GraphQL API will return the languages of a repository. I think allowing users to filter only the languages used in commits made by their user account would improve the GraphQL API. It would provide users with more accurate Language proficiency information and improve the stats displayed by repositories like github-readme-stats. I'm unsure if this is technically possible given the current GraphQL design and performance requirements and the linguist tool but here is my proposal.Current behaviour
Current graphQL query:
Current GraphQL variables
{"login": "rickstaa"}This will return the language stats per repository.
New behaviour
Maybe an attribute like
isUser: truecould be added for fetching user-specific language information.New graphQL query:
New GraphQL variables
{"login": "rickstaa"}Beta Was this translation helpful? Give feedback.
All reactions