Add language to issue on explore

[vczb]

Description

Why

I like to know what projects use React stack, so i propose its be possible add tags or language to set additional info.

Maybe can auto-import from the git code language or topics

examples:

Level

Medium

Current behavior

I need open project one by one to know if its in React

Expected behavior

Easy way to know what language and main stacks the project use

Nice to have: filter by tag/language/etc

Useful links

https://github.com/topics

How to reproduce the user scenario

• Scenario 1
  • Open explore
  • Look all issues
  • Know the project language
  • Find if necessary

What you will need to complete this issue

Backend + Frontend

[Dheeraj4103]

Hey @alexanmtz Can I work on this issue ?

[alexanmtz]

hey @Dheeraj4103 , thanks for your interest in this one, let me check with @RemyaManoharan, are you still working on this?

[alexanmtz]

Hey, @Dheeraj4103, you can work on this one. It's pretty challenging, but follow the same approach for the Labels feature we implemented.

Github has the languages for the repository that you should extract to provide the languages. So maybe it's something to be added to the project not the issue.

As we do with Labels, you must work from the backend to create a new table and filter the languages on the UI.

Let me know if you need help!

I will add a bounty for this one 👌

[Dheeraj4103]

Sure @alexanmtz I will work on it, yes it seems challenging but I will refer to Labels feature to do it.
But it might take some time for me to do it, as I have joined a new organization this week.
Hope you are okay with it.

[alexanmtz]

Yes @Dheeraj4103, take your time and let me know if you need anything

[Dheeraj4103]

Hey @alexanmtz, can you help me to understand the flow on Label component. As it will help me to work on language feature.
As languages are already present in label. If I understand the flow of Label, then I can filter out languages from label data.

[alexanmtz]

Hey @Dheeraj4103, thanks for reaching out.

It would be best to use the label just as a reference, but it's an entirely different model called 'programming languages.' As a label, we get from Github API when fetching a task, and you need to do the same with Languages, which it's defined on the Github API.

The label sometimes includes languages because it's generic, but they are different, the languages from Github return a list of the programming languages used on that repo. So, the idea is to have a dropdown to select programming languages from this programing language, and for the label you don't have to do anything, just inspiration of how to do it :)

It's an end-to-end task where you need to create the language model, migrations, and consume it when fetching a task from Github and getting the languages from the repository using the API (I guess for labels we get labels from the issue, so it is a little bit different logic).

Then, when exploring tasks in our issues list, they will list in a dropdown and filter those languages.

Let me know if you need any extra clarifications.

[Dheeraj4103]

Hey @alexanmtz Sorry, for replying this late, actually I was busy with my work.
Actually In October I have figured it out that how I can use GitHub API to get languages.
Could you please help me to create a new table and Migration so that I can add languages for rest of task.

[alexanmtz]

hello @Dheeraj4103 , sure, let's go through it.

• You need to create a migration sequelize migration:create --name modelname
• Create a model
• Run the migration npm run migrate and npm run migrate-test
• Use the model to add Programming languages to the table when syncing with Github
• Get the dropdown and filters based on these languages populated on the model.

As I mentioned before, you can always use the Label model as reference, because they will be very similar.

Let me know if you have any questions.

[Dheeraj4103]

Hey, @alexanmtz can we take a google meet this weekend, so that you can help me to understand the flow, when a new Issue is added, because this is my first time contributing to large code base.

It will be a great help if we could talk, because then I can clear my doubts in one session.