Hey @knitesh
I just looked at the style guides you picket because I´m pretty much in the same situation. For pure JS I was also using the style guide from AIRBNB. But I was also looking for guides which are more dedicated to React.
The first one "Khan" and most of the the others as well, they are pretty old fashioned. They use a lot of class components, which I don´t do anymore. I´m only using (stateful / stateless) function components. So this one is nothing for me. I don´t think that we should put energy in class components. They are more bloaded and you can achieve pretty much the same with hooks and function components.
I wasnt able to find a dedicated function component style guide. As well as something on "how small" a component should be. But anyway, they are good to get a first glance of how to structure your project and you get a basic idea of how to arrange your code in the project. So for that its good.
True, my objective is pick the idea and create a functional based style-guide, as, I also don't use class component and online you can find only class component guide.
The Airbnb one, it is ... and standardjs.com/ although I'm mostly a tab person :) @spotnick
this one maybe little old fashioned too, but in a shiny old timer way, not thé rusty kind. Just skip the class component parts.
Anyway, don't hesitate much just pick one and go with it. It's good to have ground rules, but not always important what are they. Think the pointless space/tab wars... Sooo many smart (are they?) people wasted
Hey @knitesh I just looked at the style guides you picket because I´m pretty much in the same situation. For pure JS I was also using the style guide from AIRBNB. But I was also looking for guides which are more dedicated to React.
The first one "Khan" and most of the the others as well, they are pretty old fashioned. They use a lot of class components, which I don´t do anymore. I´m only using (stateful / stateless) function components. So this one is nothing for me. I don´t think that we should put energy in class components. They are more bloaded and you can achieve pretty much the same with hooks and function components.
I wasnt able to find a dedicated function component style guide. As well as something on "how small" a component should be. But anyway, they are good to get a first glance of how to structure your project and you get a basic idea of how to arrange your code in the project. So for that its good.
True, my objective is pick the idea and create a functional based style-guide, as, I also don't use class component and online you can find only class component guide.
So keep an eye for one of my new post :)
Alrgith I do that :)
The Airbnb one, it is ... and standardjs.com/ although I'm mostly a tab person :)
@spotnick this one maybe little old fashioned too, but in a shiny old timer way, not thé rusty kind. Just skip the class component parts.
Anyway, don't hesitate much just pick one and go with it. It's good to have ground rules, but not always important what are they. Think the pointless space/tab wars... Sooo many smart (are they?) people wasted
True :) thanks for that! :)