Closed joshuamabina closed 5 years ago
Should we open a new Git repository for the week 3 challenge or continue pushing our react codes in our existing repository?
Should we open a new Git repository for the week 3 challenge or continue pushing our react codes in our existing repository?
Hello @Abk47
Thank you for this.
Proceed with the already created ride-my-way repository.
Should we open a new Git repository for the week 3 challenge or continue pushing our react codes in our existing repository?
Hello @Abk47
Thank you for this.
Proceed with the already created ride-my-way repository.
I assume we create a new branch for react implementation and then push to that branch?
We create it in different branch, am i right?!..
Should we open a new Git repository for the week 3 challenge or continue pushing our react codes in our existing repository?
Hello @Abk47 Thank you for this. Proceed with the already created ride-my-way repository.
I assume we create a new branch for react implementation and then push to that branch?
Very thoughtful of you @lupyana.
Yes. We will continue to use the github flow:
Thank you very much for this.
I also recommend this GitHub issue as resource.
Got no question for today, still working on a weekly challenge but I want to appreciate you guys for awesome work that you are doing @forlooptanzania
Good starting point to learn react https://reactjs.org/docs/getting-started.html#thinking-in-react
I have understood the recommendations on how to structure our commits. We can do various references to issues while committing our changes, that ties back to the issues for reference on what has been done.
Two questions:
ben is it necessary every time we simple changes to make a commit about it?
I would love to appreciate Ben and Joshy for awesome explains and of course Lupyana for raising some technical questions. You guys are doing some amazing work. Than you!
Thank you Ben for awesome explanation
I have understood the recommendations on how to structure our commits. We can do various references to issues while committing our changes, that ties back to the issues for reference on what has been done.
Two questions:
- Is it good practice to use the closes issue tag when committing changes, or reserve that to pull requests
- After every feature should a PR be issued?
It good to to close the issue/feature in PR since you can implement a single feature or fix a single bug using multiple commits so it better to close/fix that feature or issue using a PR
Also it is a good practice to have a feature branch and create a PR once you are done with it
The default branch is considered the base branch in your repository, against which all pull requests and code commits are automatically made, unless you specify a different branch.
Any recommendation in the use of Stateful component and stateless component?!
Any recommendation in the use of Stateful component and stateless component?!
ReactJS difference between stateful and stateless - StackOverflow
Git only takes full responsibility for your data when you commit. If you fail to commit and then do something poorly thought out, you can run into trouble. Additionally, having periodic checkpoints means that you can understand how you broke something.
... a well-crafted Git commit message is the best way to communicate context about a change to fellow developers (and indeed to their future selves).
Given that:
During development, it is good practice to split huge files into separate modules; because going through a huge file with code is extremely undesirable.
During production, the client (browser) should be able to make one request to your server to load your scripts instead of making multiple requests to load your page.
Webpack, allows you to split your code into separate modules during development and then bundle them into one file for the client (browser) to consume, during production. This is highly favorable instead of making multiple requests to your server to load the page.
EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs.
ESLint is a library used for linting JavaScript and JSX code.
Linting is the process of running a program that will analyse code for potential errors.
Use next generation JavaScript, today.
Allows you to write ES6+ code and [transpile]() to compatible versions for the browser.
Babel.js - The compiler for next generation JavaScript.
Pull requests play an important role during code reviews. They exist to suggest to the author or maintainer of the repository to, request to pull from my repository.
Important Note Make pull request against the develop
branch. As a safe measure, ensure that the develop branch is the default branch.
Learn about default branches here.
Thinking in React is a great resource.
In our ride-my-way repositories, we must create a ui folder; this is where all our templates will go into. We will then proceed to use create-react-app to scaffold out the necessary react files.
Hi all!
Kindly drop in any question around the topics below:
We will be joining a Q & A session with @BenMaruchu at 17:00hrs EAT. Please attend without fail to be able to unlock and unblock your world-class developer potential.
Join Zoom Meeting using https://andela.zoom.us/j/668566256