Make Algorithm Component.

[prathmeshkhandelwal1]

• Use GitHub API for fetching algorithms from IIITV/algos repo.

[prathmeshkhandelwal1]

@iiitv/batch-of-2023 See if anyone can pick this up?

[raghusodani]

can I work on this after working on the previous issue :)?

[prathmeshkhandelwal1]

can I work on this after working on the previous issue :)?

Sure, but i will assign this after completing that issue, that won't be a bother ig ;)

[raghusodani]

you can assign it now @prathmeshkhandelwal1

[prathmeshkhandelwal1]

you can assign it now @prathmeshkhandelwal1

Sure

[raghusodani]

I have to implement the left component and not the editor part?? or both??
@prathmeshkhandelwal1

[raghusodani]

[raghusodani]

@prathmeshkhandelwal1 can u clarify the above issue??

[prathmeshkhandelwal1]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

[raghusodani]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

Then, I have to make folder based on iiitv/algos not according to design

[prathmeshkhandelwal1]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

Then, I have to make folder based on iiitv/algos not according to design

I am not clear about your point, can you clarify a bit?

[raghusodani]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

Then, I have to make folder based on iiitv/algos not according to design

I am not clear about your point, can you clarify a bit?

In design, Algorithms are categorized based on their basic data structure(tree, graph), but iiitv/algos has no such bifurcation.
if we implement the design version of component, we need to make changes in iiitv/algos repo.

[prathmeshkhandelwal1]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

Then, I have to make folder based on iiitv/algos not according to design

I am not clear about your point, can you clarify a bit?

In design, Algorithms are categorized based on their basic data structure(tree, graph), but iiitv/algos has no such bifurcation. if we implement the design version of component, we need to make changes in iiitv/algos repo.

Okk, i will take a look into this and let you know ny EOD

[raghusodani]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

Then, I have to make folder based on iiitv/algos not according to design

I am not clear about your point, can you clarify a bit?

In design, Algorithms are categorized based on their basic data structure(tree, graph), but iiitv/algos has no such bifurcation. if we implement the design version of component, we need to make changes in iiitv/algos repo.

Okk, i will take a look into this and let you know ny EOD

any updates??

[prathmeshkhandelwal1]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

Then, I have to make folder based on iiitv/algos not according to design

I am not clear about your point, can you clarify a bit?

In design, Algorithms are categorized based on their basic data structure(tree, graph), but iiitv/algos has no such bifurcation. if we implement the design version of component, we need to make changes in iiitv/algos repo.

Okk, i will take a look into this and let you know ny EOD

any updates??

I took a look into this, Seems perfectly fine to me, you can get all heading from https://api.github.com/repos/iiitv/algos/contents and the files inside them from https://api.github.com/repos/iiitv/algos/contents/<heading_name> @raghusodani

[raghusodani]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

Then, I have to make folder based on iiitv/algos not according to design

I am not clear about your point, can you clarify a bit?

In design, Algorithms are categorized based on their basic data structure(tree, graph), but iiitv/algos has no such bifurcation. if we implement the design version of component, we need to make changes in iiitv/algos repo.

Okk, i will take a look into this and let you know ny EOD

any updates??

I took a look into this, Seems perfectly fine to me, you can get all heading from https://api.github.com/repos/iiitv/algos/contents and the files inside them from https://api.github.com/repos/iiitv/algos/contents/<heading_name> @raghusodani
I already did this. My doubt is that for eg currently bfs, dfs, and other algos are independent and not under graph folder but in our product we want to ensure that all graph algorithms should be in one place

[prathmeshkhandelwal1]

I have to implement the left component and not the editor part?? or both?? @prathmeshkhandelwal1

Both will be better

Then, I have to make folder based on iiitv/algos not according to design

I am not clear about your point, can you clarify a bit?

In design, Algorithms are categorized based on their basic data structure(tree, graph), but iiitv/algos has no such bifurcation. if we implement the design version of component, we need to make changes in iiitv/algos repo.

Okk, i will take a look into this and let you know ny EOD

any updates??

I took a look into this, Seems perfectly fine to me, you can get all heading from https://api.github.com/repos/iiitv/algos/contents and the files inside them from https://api.github.com/repos/iiitv/algos/contents/<heading_name> @raghusodani
I already did this. My doubt is that for eg currently bfs, dfs, and other algos are independent and not under graph folder but in our product we want to ensure that all graph algorithms should be in one place

I agree here with you to some extent, but as we know bfs and dfs are wide algos and they have such a huge use, so making separate folder of them is not an issue, and coming to us (those who are working on algos-web). We just have to use folder names as head and files inside them as items. @raghusodani

[raghusodani]

Ok then I will implement it as it is

[prathmeshkhandelwal1]

Sure